External @includes in global ~/.claude/CLAUDE.md never prompt for approval
Resolved 💬 1 comment Opened Apr 5, 2026 by andyrosa2 Closed Apr 5, 2026
Preflight Checklist
- [X] I have searched existing issues and this hasn't been reported yet
- [X] This is a single bug report (please file separate reports for different bugs)
- [X] I am using the latest version of Claude Code
What's Wrong?
External @ includes in the global ~/.claude/CLAUDE.md are silently ignored — no approval prompt is shown, and the included files are never loaded into context.
Example ~/.claude/CLAUDE.md:
@c:\dfc\gh\agent_instructions\core-behavior.instructions.md
@c:\dfc\gh\agent_instructions\coding-standards.instructions.md
@c:\dfc\gh\agent_instructions\example-user-context.instructions.md
The files exist and are readable. Each contains a canary string that should appear in responses. The canary strings never appear, confirming the includes are not resolved.
Per the docs, external includes should prompt for approval the first time. The prompt never appears.
What Should Happen?
Claude Code should either:
- Prompt the user to approve external includes from the global CLAUDE.md, then load them
- Or warn that the includes were skipped
Steps to Reproduce
- Add
@/some/external/path/file.mdto~/.claude/CLAUDE.md - Ensure the file exists and contains a unique canary string
- Start a new Claude Code session
- The canary string never appears — the include is silently ignored with no approval prompt
Claude Code Version
Latest stable
Platform
Windows 10 Enterprise
Operating System
Windows
Terminal/Shell
Windows Terminal (bash)
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗