Claude Code now reads AGENTS.md if Claude.md missing

What Happened

Claude Code now falls back to an AGENTS.md file when a project lacks Claude.md. Agents defined in AGENTS.md load automatically, eliminating the need for a placeholder file. The changelog noted this update as a fix for configuration errors.

Why This Matters for Builders

• Less manual setup: Skip creating a dummy Claude.md when all agent logic lives in AGENTS.md. Saves time in CI/CD pipelines.
• Fewer runtime failures: Missing Claude.md used to stop agents from loading. The fallback keeps them discoverable and prevents silent production crashes.
• Cleaner version control: A single source of truth (AGENTS.md) reduces merge conflicts and simplifies history in large teams.
• Predictable tooling: Automation platforms like n8n can rely on one file name, streamlining scripts and deployment pipelines.

FAQ

Q: Does this change affect existing projects that already have Claude.md?

A: No. If Claude.md exists, the system uses it. The fallback only triggers when that file is absent.

Q: Will the fallback work with nested agent definitions or only top‑level ones?

A: The system parses the entire AGENTS.md file, so any agent definitions—nested or flat—are loaded.

Q: How should I update my deployment scripts to take advantage of this?

A: Reference AGENTS.md instead of Claude.md in your build or deployment steps. If you still create a Claude.md, the system will prioritize it, so pick one convention for consistency.

---

Originally published on Automations Cookbook.