Short answer
Yes. Cursor reads AGENTS.md in the project root and in subfolders. Use AGENTS.md for plain project instructions that Cursor, Codex, and (since v2.1.277) Claude Code can all read. Use Cursor project rules in .cursor/rules when you need Cursor-only control, such as rules that apply only to certain files. Many teams use both.
Words used in this guide
- AIPM: a tool that installs and updates reusable AI instructions.
- Repository or repo: a project folder whose changes are saved and tracked.
- Git: a tool that records file changes so people can review or undo them.
What this means
Does Cursor support AGENTS.md?
Yes. Cursor documents AGENTS.md as a simple alternative to .cursor/rules. Put one AGENTS.md in the project root, and add more AGENTS.md files in subfolders when one part of the code needs its own instructions. Cursor combines nested files with their parent folders, and the more specific file wins when they conflict.
AGENTS.md is the shared, plain-text option
AGENTS.md is a normal Markdown file with no frontmatter. It can list build commands, test steps, code style, and limits. Because it is not tied to one editor, other coding agents can read it too. OpenAI Codex reads AGENTS.md, and Claude Code v2.1.277 and later reads it when the project has no CLAUDE.md or CLAUDE.local.md.
Cursor rules give you more control
Cursor project rules live in .cursor/rules as .mdc files. Each rule has frontmatter that decides when it applies: always, when the agent decides it is relevant, when a matching file is open (globs), or only when you @-mention it. A plain .md file in .cursor/rules is ignored, so use AGENTS.md if you want plain Markdown.
Use both with one clear owner
Keep shared repo facts in AGENTS.md. Put only Cursor-specific or file-scoped behavior in Cursor rules. AIPM does not install AGENTS.md or Cursor rules; if a repeatable task is used in many repos, make it a skill and install the same reviewed version with AIPM.
Simple steps
- Write the instructions that every coding agent needs.
- Put those shared instructions in AGENTS.md at the project root.
- Add nested AGENTS.md files only where a folder needs different instructions.
- Add Cursor project rules (.mdc) only for Cursor-only or file-scoped behavior.
- If the project also has a CLAUDE.md, add @AGENTS.md to it so Claude Code reads the shared file.
- Review both files in Git and remove repeated text.
Where to go next
If you want to try this in a real project, start with how to use AIPM and the command reference. If you want to share your own workflow, read the publishing guide.
FAQ
Does Cursor read AGENTS.md?
Yes. Cursor supports AGENTS.md in the project root and in subdirectories. Nested files apply when Cursor works with files in that folder.
Does Claude Code read AGENTS.md?
Yes, from Claude Code v2.1.277. By default it reads AGENTS.md only when there is no CLAUDE.md, .claude/CLAUDE.md, or CLAUDE.local.md in the working directory or above it. If you keep a CLAUDE.md, import the shared file with @AGENTS.md. Full rules and fixes: does Claude Code read AGENTS.md?
Should I use AGENTS.md or Cursor rules?
Use AGENTS.md for plain instructions every agent should see. Use Cursor rules when you need Cursor-only features such as glob-scoped or manually attached rules.
Are .cursorrules files still recommended?
No. Cursor treats .cursorrules as legacy. New projects should use project rules in .cursor/rules or a simple AGENTS.md file.