Feature Request: Support AGENTS.md
github.com
Feature Request: Support AGENTS.md
1–10 of 236 posts
Re: Feature Request: Support AGENTS.md
#2choose not to support them in return if it is a real problem
otherwise a simple symlink from AGENTS.md -> CLAUDE.md works well enough
disclaimer, I only use open weight models and open source harnesses so have no stake in this either way, other than I support devs who do use claude (for now) and the symlink solution has worked fine for us
Re: Feature Request: Support AGENTS.md
#3My Claude.md has one line that says to read agents.md, this is a bit of a nothingburger
Re: Feature Request: Support AGENTS.md
#4My Claude.md has one line that says to read agents.md, this is a bit of a nothingburger
You can save a tool call by just making it a symlink
Re: Feature Request: Support AGENTS.md
#5My Claude.md has one line that says to read agents.md, this is a bit of a nothingburger
well I generally agree, pretty much every other harness supports looking for the various alternatives and uses them
I see this obstinance as an intent signal and one of the smaller bullet points I have for avoiding Ant
Re: Feature Request: Support AGENTS.md
#6how does agents.md work for subagents and swarms? is it actually that useful?
Re: Feature Request: Support AGENTS.md
#7Also the skills are different. it's quite annoying!
Re: Feature Request: Support AGENTS.md
#8Re: Feature Request: Support AGENTS.md
#9The obvious reason is that they would prefer to have CLAUDE.md files in every repo (even if it's just a symlink to AGENTS.md). It serves as a free advertisement for them. Same reason as for auto-adding attribution text in commit messages, etc. It's the "Sent from my iPhone" of our time.
Re: Feature Request: Support AGENTS.md
#10My Claude.md has one line that says to read agents.md, this is a bit of a nothingburger
Mine does too because, while I use Codex, my non-technical co-founder uses Claude. I find Claude still will randomly ignore instructions in there. Basic things like how to name a PR or what to put in a PR description.
My experience is that what you're suggesting isn't a perfect solution.