Yes, current Claude Code supports AGENTS.md, but a file’s presence does not guarantee that it loads. The default favors project CLAUDE.md instructions. A CLAUDE.md, .claude/CLAUDE.md or CLAUDE.local.md in the working directory or an ancestor can affect the fallback to AGENTS.md. 1
Check configuration before renaming files
Check your Claude Code version and open Project instructions in /config. Current settings can load both formats instead of using the default either/or behavior. Older installations or disabled support can behave differently.
When a project keeps CLAUDE.md but shares instructions through AGENTS.md, an explicit import is available:
@AGENTS.md
That is different from writing “read AGENTS.md when needed”: a prose request leaves the decision to the agent. 1
Verify with a harmless task
Use one observable convention, such as the project’s existing test command. Start a fresh conversation and check the loaded context and actual actions. Do not test instruction precedence with production data or secrets.
Keep the rule small enough to diagnose. Adding several competing files makes it harder to distinguish a loading problem from conflicting instructions. A loaded file is also not an enforcement mechanism: important constraints still need permissions, review and tests. 2
