5 ms·
Make sure to check out https://agent-rules.org/ https://agent-rules.org/ as well for more background on this initiative. More and more tools are adopting the st
by _mu 1y ago
Make sure to check out https://agent-rules.org/ https://agent-rules.org/ as well for more background on this initiative. More and more tools are adopting the standard.
Amp used to have an "RFC 9999" article on their website for this as well but the link now appears to be broken.
You can symlink your Cursor / Windsurf / whatever rules to AGENTS.md for backwards compatibility.
- sqs 1y agoThat draft RFC you mention is superseded by https://agents.md https://agents.md. Now that Amp uses AGENTS.md (https://x.com/sqs/status/1957945824404729997 https://x.com/sqs/status/1957945824404729997), I made all the former agent file stuff on https://ampcode.com https://ampcode.com just redirect to https://agents.md https://agents.md.
- _mu 1y agoGotcha - this is what I had in my history: https://ampcode.com/AGENT.md https://ampcode.com/AGENT.md For me, that gives a 404 with no obvious way to get to https://agents.md https://agents.md, I think either a hyperlink or redirect would be nice to have as well.
- tomComb 1y agoOk, I looked at your agent-rules and it sounds good except for a couple things ... "Guidance for Use" Your preference for bullet lists over headers is odd. This comes down to what works best with the models - they are interpreting it. This is a moving target. If you believe that your suggestion works best you should provide some sort of evidence. The default would be to not even get into that sort of thing. Non-Hierarchical AGENTS.md Claude-code, Gemini, and GHCP all support hierarchical context files. Your proposal and this new one from OpenAI and friends do not, and I think that is a shame.
- _mu 1y agoI did not write agent-rules, I'm just linking to it.