/reload-settings command to hot-reload settings.json without restarting

Resolved 💬 3 comments Opened Apr 26, 2026 by timbrigham Closed Apr 30, 2026

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.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗