AGENTS.md generator
Build an AGENTS.md that Codex, Cursor, Copilot, Antigravity, Devin, Kiro, OpenCode, Amp and more read natively, plus the CLAUDE.md bridge and a Cursor rule stub. Runs in your browser.
1.
AGENTS.md 2.
CLAUDE.md 3.
.cursor/rules/agents.mdc 4.
.gemini/settings.json Shell
setup.sh What makes a good AGENTS.md
- Commands first. Exact install, build, test and lint commands are the facts an agent can't infer; the linter flags files without them.
- Specific, checkable rules. "Use pnpm" beats "use the right package manager".
- Short. It loads on every request; Codex stops at 32 KiB, Claude Code suggests under ~200 lines per file.
- Not a security boundary. Pair safety rules with real permission rules: see the per-agent presets in the config hub.
Where each agent looks
Root AGENTS.md works natively in Codex CLI, Cursor, GitHub Copilot, Devin Desktop (ex-Windsurf), Cline, Roo Code, Kilo Code, OpenCode, Amp, Kiro, Jules, Factory Droid. For the rest, see one AGENTS.md for every agent.
FAQ
What should an AGENTS.md file contain?
The commands an agent cannot guess (install, build, test, lint), the project layout, coding conventions that differ from defaults, and hard rules such as never force-pushing or reading .env files. Keep it short: it is loaded into every session.
How do I make Claude Code use my AGENTS.md?
Create a CLAUDE.md whose first line is @AGENTS.md, or symlink CLAUDE.md to AGENTS.md. Claude Code v2.1.277+ also reads AGENTS.md directly when no CLAUDE.md exists.
Do I need a .cursor/rules file if I have AGENTS.md?
No. Cursor reads AGENTS.md in the project root and subdirectories. Use .cursor/rules/*.mdc only for rules that should apply to specific globs.
Is my data sent anywhere?
No. The generator runs entirely in your browser; nothing you type is uploaded. We only count that the button was used.