1300 166 138 Tell us what you need
News / AI Agents

Switching between Codex and Claude Code just got easier

By Monika Tantau • Published 2 months ago
Switching between Codex and Claude Code just got easier

Key takeaways

• Claude Code 2.1.277 reads AGENTS.md whenever a project has no CLAUDE.md file
• AGENTS.md is the open instructions format used by Codex, Cursor, Gemini CLI and GitHub Copilot
• If both files exist CLAUDE.md still wins, and the fallback can be switched off
• It does not work yet when Claude runs through Amazon Bedrock, Google Vertex or Microsoft Foundry

Most Read

Teams that use more than one AI coding agent now have one less file to maintain. Claude Code reads AGENTS.md, the instructions file OpenAI’s Codex and a long list of other tools already use, whenever a project has no CLAUDE.md, according to Anthropic.

The change shipped in version 2.1.277 on 18 September. In practice, a repository set up for Codex now works in Claude Code without anyone rewriting the house rules first.

What Anthropic changed

Claude Code has always looked for a CLAUDE.md file to learn a project’s conventions: how to build it, how to run the tests and which style to follow. If that file is missing, it now falls back to AGENTS.md.

The check works folder by folder. As Anthropic’s Thariq put it when announcing the change on X, if there is no CLAUDE.md in a folder, Claude will check for and use AGENTS.md, which matters for repositories that keep instructions in several directories.

If a folder has both, CLAUDE.md still wins. The fallback can be switched off under Project instructions in Claude Code’s config menu, which matters for teams that deliberately keep different instructions for each tool.

What AGENTS.md actually is

AGENTS.md is a plain Markdown file with a predictable name. It came out of work by OpenAI’s Codex team, Google’s Jules, Cursor, Amp and Factory, and is now looked after by the Agentic AI Foundation under the Linux Foundation, according to the project.

The content is whatever a new developer would need on day one: build and test commands, code style guidelines, testing instructions and security considerations. There is no required structure beyond it being standard Markdown, which is part of why so many tools adopted it.

More than 60,000 open source projects already use it, and it is read by Codex, Cursor, Gemini CLI, GitHub Copilot’s coding agent, Devin, Windsurf and JetBrains’ Junie, among others. Claude Code was the obvious name missing from that list.

Why switching gets easier

Why switching gets easier

Until now, a team trying both tools kept two copies of the same instructions or a pointer file linking one to the other, and keeping them in step was one more chore. One file means one source of truth, whichever agent a developer opens that morning.

For a team on Codex today, the move is short. Open the repository in Claude Code and it picks up the existing AGENTS.md. If you later want instructions that only Claude should see, add a CLAUDE.md alongside it and that file takes over for Claude, while Codex keeps reading AGENTS.md.

It also lowers the cost of comparing them properly. A fair test is now simply opening the same repository in both, and our Claude Code vs Codex comparison covers what to look for when you do.

Why Australian businesses should care

There is a local catch. The fallback does not yet apply when Claude runs through Amazon Bedrock, Google Vertex or Microsoft Foundry, and Bedrock in the Sydney region is a common way for Australian organisations to keep Claude processing onshore, as set out in our guide to AI data residency.

If your developers reach Claude Code through Bedrock, keep the CLAUDE.md for now. For everyone else it is a good moment to tidy the instruction files, because they set the rules an agent follows inside your code base. Deciding those rules deliberately is part of any sensible AI consulting work on coding agents.

A small change with a clear direction

Coding agents are converging on shared conventions, and that is good news for buyers. The less work it takes to move a project from one tool to another, the more each vendor has to compete on quality rather than on lock in.

Scroll to Top