Post

That fallback catches people out: a stray ~/CLAUDE.md quietly sidelines the AGENTS.md they thought was in charge. How did you find out, a rule that suddenly stopped being followed?

/memory only tells you after the fact, which is late if the stray file has been steering things for a week. Worth checking before you trust any instruction you've added.

the checker in the post walks from your working dir up to / and shows which file Claude Code should load, with no session needed. Or skip the fallback: a repo CLAUDE.md that just says @AGENTS.md loads it whatever sits above the repo indeed

claude.mdOverview - Claude Code DocsClaude Code is an agentic coding tool that reads your codebase, edits files, runs commands, and integrates with your development tools. Available in your terminal, IDE, desktop app, and browser.

A one-line CLAUDE.md that points at @AGENTS.md is a tidy way to stop guessing which file wins. Does the checker also flag a file higher up the tree that adds rules the repo never asked for?

The checker shows which file should load, but we’d need to verify whether it also flags rules added by ancestor files. You’re right that those are different checks—a clear warning would be useful.

Finding out a week late is the real cost there. What would you want as the early warning: a list of every instruction file loaded at the start of each session, or a flag when a new one appears?