GUIDE

One AGENTS.md for Claude Code, Codex and Cursor

Write your agent rules once and have every coding agent you use read them. Checked against the official docs on Oct 19, 2026. Updated Oct 23 with Agent Skills.

Why bother

Most people don't stick to one agent anymore. Theo shared that over 60% of T3 Code users who used Codex in the last 2 weeks also used Claude Code (source). If your rules live in three different files, they drift apart, and one agent ends up following last month's rules.

Who reads AGENTS.md

Setup in 3 steps

  1. Put your rules in AGENTS.md at the repo root: setup commands, the one command that checks your work, code style, and what the agent must never do.
  2. Delete or merge any old project CLAUDE.md into it, so Claude Code doesn't skip AGENTS.md.
  3. If you need a CLAUDE.md too, open /config in Claude Code and set Project instructions to claude-md-and-agents-md so it reads both.
# check what Claude Code loaded: start a session and look for
# "no CLAUDE.md found; AGENTS.md loaded: /path/to/repo/AGENTS.md"
claude

Gotchas

AGENTS.md or Agent Skills?

Use both. They do different jobs, and since Oct 22, 2026 both live at the Linux Foundation's Agentic AI Foundation, next to MCP (AAIF announcement).

Rule of thumb: if it applies to every task in the repo, put it in AGENTS.md. If it's a repeatable procedure you'd hand to a specialist, make it a skill. Skills can ship scripts, so read any skill you didn't write before you install it.

A starter AGENTS.md that keeps builds green

Our free Checkpoint Loop is an AGENTS.md plus a one-command check script. The agent works on a branch in small steps and only commits when the check passes. Making a game? Pack #001 ($19) adds an AGENTS.md for game projects, a playtest agent and a fun review.

Next: make your coding agent prove it's done, a verification checklist based on how the Claude Code team reviews code.

Get the free Checkpoint Loop

Get the patch notes free →

Free, weekly, one-click unsubscribe. We note changes like this one every week.