Feature Request: Hot reload configuration (/reload command)

Resolved 💬 3 comments Opened Jan 10, 2026 by bautrey Closed Jan 14, 2026

Feature Request: Hot reload configuration

Problem: Settings changes (settings.json, settings.local.json, CLAUDE.md) require a full session restart to take effect. When running multiple concurrent sessions (12+ in my case), this is disruptive and breaks workflow continuity.

Current behavior:

  • Configuration is loaded once at session start
  • Auto-compaction summarizes conversation but doesn't reload config
  • Only way to pick up config changes is --resume with a new session

Proposed solution:

  • Add /reload command to re-read all configuration files:
  • ~/.claude/settings.json
  • ~/.claude/settings.local.json
  • Project and global CLAUDE.md files
  • Hooks configuration
  • Optionally: auto-reload configuration on compaction events

Use cases:

  1. Iterating on permissions without losing conversation context
  2. Updating CLAUDE.md instructions mid-session
  3. Adding/modifying hooks while working
  4. Managing configuration across many concurrent sessions

Workaround today: Exit and restart each session with --resume, which works but adds friction when managing multiple sessions.

---
Submitted via Claude Code

View original on GitHub ↗

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