Tool converting CLAUDE.md to AGENTS.md format
Built for Engineering teams using Claude Code alongside other AI coding agents (Codex, Cursor, Amp) who need standardized agent onboarding across tools..
“Codex, Amp, Cursor, and others are starting to standardize around AGENTS.md (https://agents.md/) — a unified Markdown file that coding agents can use to underst…”
The receipts — real demand
“Codex, Amp, Cursor, and others are starting to standardize around AGENTS.md (https://agents.md/) — a unified Markdown file that coding agents can use to understand a codebase. By contrast, CLAUDE.md feels too specific to Claude Code. It doesn’t work as well when collaborating with other developers who aren’t using Claude Code. ”
Full dossier
Unlock the full dossier — free
Every corroborating quote, the source receipts, and the community echo. One email, no payment.
Why this is a gap
Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.
The market
Engineering teams using Claude Code alongside other AI coding agents (Cursor, Codex, Amp) need to convert CLAUDE.md to AGENTS.md format for standardized onboarding. No search volume, but the signal is emerging: AGENTS.md is becoming a unified standard.
Competition & the opening
No conversion tool exists (1/10 crowded). CLAUDE.md and AGENTS.md are both nascent formats. The gap: a translator that maps Claude-specific directives to the unified AGENTS.md schema.
What's hard to build
Both formats are still evolving; AGENTS.md is a moving target, and CLAUDE.md has no formal spec. Building a durable converter requires staying in sync with both standards. The real challenge: handling semantic loss (Claude-specific instructions may not map cleanly to AGENTS.md) and validation that converted agents work across tools.
Why now
AGENTS.md is emerging as industry standard but existing CLAUDE.md files create lock-in; migration gap exists right now.
How you'd monetize
Free CLI tool, $29/mo hosted conversion service