Newly created ~/.claude/settings.json is ignored until restart — permission rules silently inert

Status Fixed / completed
Maintainer reply None cached
Activity 3 comments · opened Jun 10, 2026 · closed Jun 10, 2026

If ~/.claude/settings.json does not exist when a session starts, creating it mid-session has no effect: the settings watcher only watches directories that already had a settings file at startup. Practical impact: the agent writes permission allow rules at the user's request, both believe prompts will stop, and the user sits through dozens more permission prompts until someone realizes a full restart is required to load the file.

Requests:

  1. Watch for settings-file creation, not only modification.
  2. Failing that, surface explicit feedback when a settings file appears mid-session ("settings file created — restart or open /hooks to load").

Environment: macOS 26.5 (arm64), Claude Desktop 1.9659.2 with bundled Claude Code; GitHub integration connected.

Related settings-loading issues, not duplicates: #58443 (symlinked settings.json regression), #64699 (hooks stop firing after editing settings.local.json) — this issue is specifically the file-creation case: a settings.json born mid-session is never watched.

View original on GitHub ↗

3 Comments

github-actions[bot] · 4 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/65953
  2. https://github.com/anthropics/claude-code/issues/64699
  3. https://github.com/anthropics/claude-code/issues/62656

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

gkriegspeedbay · 4 months ago

Closing as duplicate of #65953 (mid-session settings.json changes not enforced until restart) and the #62656 reload feature request. The file-creation-specific datapoint is posted on #65953.

github-actions[bot] · 2 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.