Claude Code adds AGENTS.md support

Claude Code now reads AGENTS.md if there is no CLAUDE.md

Bottom line: As of the September 18 2026 release, Claude Code falls back to an AGENTS.md file when a project lacks a CLAUDE.md. This change removes a mandatory step, lets users keep their instruction files provider‑agnostic, and brings Claude Code in line with community expectations for a standard agent‑definition format.

---

Why the change matters

• Reduced friction – Previously every Claude Code project needed a CLAUDE.md at the repository root. Users who preferred the more generic AGENTS.md (or who migrated from other harnesses) had to create a symlink or duplicate the file. The new fallback eliminates that extra maintenance.
• Alignment with emerging conventions – Several developers have advocated for a neutral AGENTS.md name that works across Claude, Codex, Gemini, and other AI‑code assistants. By honoring AGENTS.md out‑of‑the‑box, Anthropic signals responsiveness to community standards.
• Cleaner project layouts – Projects can now store a single source of truth for agent instructions without cluttering the repo with symlinks or duplicate files.

---

What the release notes say

September 18, 2026 – Added AGENTS.md support: in a project with no CLAUDE.md, Claude Code reads AGENTS.md instead; change it under “Project instructions” in /config (not yet on Bedrock, Vertex or Foundry).

The change is confined to the CLI and VS Code extension; cloud‑hosted Claude Code sessions on Bedrock, Vertex, or Foundry will receive the feature in a future update.

---

Community reaction on Hacker News

Commenter	Sentiment	Key points
@askonomm	Positive	“Finally doing something standards‑compliant instead of forcing users into a proprietary workflow.”
@stillpointlab	Observational	Noted that Claude Fable auto‑creates an AGENTS.md and a symlink to it, suggesting the tool already inferred the need for a neutral file.
@neverrroot	Positive	“Thanks guys, you did the right thing.”
@bcorigliano	Positive	Celebrates the move toward industry‑wide standards.
@TomGarden	Mixed	Appreciates the change but calls the previous requirement “the absolute bare minimum.”
@mococa	Critical	Argues the change is overdue and that standards should have been adopted earlier.
@clutter55561	Cautionary	Reminds users that Claude Code still won’t detect skills in .agents/skills.
@aroman	Practical	“Finally, I can delete sync-agent-docs.sh, which recursively symlinked AGENTS.md to GEMINI.md and CLAUDE.md…”
@jtbaker	Humorous	Shares a news article quoting Shopify’s CEO about possibly banning Claude Code until it respects AGENTS.md.
@mitchitized	Skeptical	Claims the change feels like a reaction to community pressure rather than genuine care.
@perganomoly	Disappointed	“The fact that it took this long to add such a basic feature is a disgrace.”
@albatross79	Sarcastic	Calls Claude Code “bloated” and doubts it will ever fully respect AGENTS.md instructions.

Overall, the sentiment is overwhelmingly positive, with most commenters welcoming the simplification and viewing it as a step toward broader interoperability.

---

How to use the new behavior

1. Create an AGENTS.md at the root of your project (or in any subdirectory you work in). Include the same instruction syntax you would have used in CLAUDE.md.
2. Remove the CLAUDE.md file or leave it absent. Claude Code will automatically detect and load AGENTS.md.
3. Configure the fallback path (if needed) via the /config panel under Project instructions – this setting is currently only available in the CLI and VS Code UI, not in Bedrock/Vertex/Foundry deployments.
4. Verify by running claude --version and then starting a session; the startup log will indicate “Reading project instructions from AGENTS.md”.

---

What does not change?

• Skill loading – Claude Code still does not automatically load skills from a .agents/skills directory. Users must continue to register skills explicitly or rely on the existing skills/ mechanism.
• Cloud‑hosted sessions – The fallback is not yet enabled on Bedrock, Vertex, or Foundry instances; those platforms will receive the update in a later patch.
• Legacy behavior – If both CLAUDE.md and AGENTS.md exist, CLAUDE.md retains priority, preserving backward compatibility for existing projects.

---

Quick checklist for existing projects

• Remove any symlinks that point CLAUDE.md → AGENTS.md.
• Ensure AGENTS.md contains the full set of agent instructions you need.
• Test a fresh Claude Code session to confirm the file is being read.
• Update any internal documentation to reference AGENTS.md as the canonical instruction file.

---

Bottom line

Claude Code’s addition of AGENTS.md fallback is a modest but meaningful quality‑of‑life improvement. It eliminates an unnecessary file, respects a naming convention that works across multiple AI‑code assistants, and demonstrates Anthropic’s willingness to listen to developer feedback. The change is already live in the CLI and VS Code extension, and the community response suggests it will be welcomed as a step toward broader standardization in the AI‑assisted development ecosystem.