When settings.json (or settings.local.json) is edited during an active session — e.g. to add a new permission allowlist entry — the change only takes effect after restarting Claude Code. This creates friction in multi-instance workflows where one instance is doing work and another is being used to manage configuration.
A /reload-settings slash command (or equivalent) would let the active session re-read its settings files in place, so permission changes take effect immediately without losing conversation context.
Use case: Two Claude Code sessions open simultaneously. Session A edits .claude/settings.json to add new Edit(**)/WebFetch(*) permissions. Session B currently has to be fully restarted to pick them up.
When
settings.json(orsettings.local.json) is edited during an active session — e.g. to add a new permission allowlist entry — the change only takes effect after restarting Claude Code. This creates friction in multi-instance workflows where one instance is doing work and another is being used to manage configuration.A
/reload-settingsslash command (or equivalent) would let the active session re-read its settings files in place, so permission changes take effect immediately without losing conversation context.Use case: Two Claude Code sessions open simultaneously. Session A edits
.claude/settings.jsonto add newEdit(**)/WebFetch(*)permissions. Session B currently has to be fully restarted to pick them up.