Feature: Auto-load files referenced in CLAUDE.md
Resolved 💬 3 comments Opened Feb 7, 2026 by crisscross82 Closed Feb 11, 2026
Problem
When CLAUDE.md references external rule files (e.g., a table of paths to ~/.config/rules/*.md), Claude Code doesn't automatically read them at session start. Each new session starts fresh with only the CLAUDE.md content, causing Claude to fall back to default behaviors instead of user-defined workflows.
Current Workaround
Users must either:
- Inline all rules directly in CLAUDE.md (makes it very long)
- Add explicit instructions like "At session start, read all files in ~/.config/rules/"
- Manually ask Claude to read the rules each session
Proposed Solution
One or more of:
- Auto-load referenced files: When CLAUDE.md contains file paths or references, automatically read them into context at session start
- Designated rules directory: Support a
.claude/rules/directory that's always loaded (similar to how.claude/CLAUDE.mdworks) - Include directive: Support an
<!-- include: path/to/file.md -->syntax in CLAUDE.md
Use Case
I maintain development workflow rules in separate organized files:
~/.config/ai-dev-standards/rules/
├── git-workflow.md
├── database.md
├── typescript.md
└── ...
My CLAUDE.md references these, but Claude doesn't know about them without explicit instructions, leading to workflow violations (wrong branch strategy, wrong commit format, etc.).
Environment
- Claude Code CLI
- Rules stored in external markdown files referenced from CLAUDE.md
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗