Live data from Hacker News

Do agents.md files help coding agents?

twitter.com

11–20 of 52 posts

Re: Do agents.md files help coding agents?

#11
The tweet misses the conclusion from the paper that handcrafted AGENTS.md might help. To me its no surprise that 100% vibed AGENTS.md are unproductive. Not reviewing your design docs is probably even worse than not reviewing your code? I've seen some AI-generated agents.md which were just plain wrong. No surprise agents perform worse after reading those.

I use AGENTS.md to make sure my agents loop effectively (tests, quality, etc). Not to describe the code / architecture.

Re: Do agents.md files help coding agents?

#13
The amount of cargo-culting around AI tooling and practices is so weird to me.

Why not just try and see? The fast feedback loop allow testing all kind of weird theories in a matter of 30m-1h during normal working sessions, most results are obvious

Re: Do agents.md files help coding agents?

#14
post #7

Earlier quoted context omitted.

The referenced paper says No.

You are absolutely right, thank you for pushing back. Upon further examination, I've confirmed that the referenced paper says no. /s

On a second thought... The result is counter-intuitive, because writing AGENTS.md (and reading if it's generated) contributes to the context in the human. So yes, AGENTS.md probably help more than the paper says, but not the way we initially frame it.

Dunno if there's a way to test that AGENTS.md help the human more than the machine.

Re: Do agents.md files help coding agents?

#17
[dupe] https://news.ycombinator.com/item?id=47034087

Paper was discussed here 4 months ago, and the linked tweet on this post doesn't add any insights and completely misses the huge caveats that come with the found result: the main benefits of using AGENTS.md files are inherently opposed to the characteristics of _median_ "public github project that has an AGENTS.md file".

Re: Do agents.md files help coding agents?

#18
post #17

[dupe] https://news.ycombinator.com/item?id=47034087 Paper was discussed here 4 months ago, and the linked tweet on this post doesn't add any insights and completely misses the huge caveats that come with the found result: the main benefits of using AGENTS.md files are inherently opposed to the characteristics of _median_ "public github project that has an AGENTS.md file".

Yeah it was a good discussion. I'm definitely on the side of "a well written agents.md is very good for the agent". The file should not be static. The agents.md from a year ago is not the right agents.md for today. Many of them are overly long, overly instructive, and include a lot of unccessary code bits.

I think it's useful for people using agent harness to regularly evaluate your skills, agent rules, and memory implementation to ensure there's no conflict across them all. Also, best to rely as little as possible on the agent to write its own agents.md.

It can be be tedious, but that's why agentic coding can still be considered a "skill".

Re: Do agents.md files help coding agents?

#19
post #13

The amount of cargo-culting around AI tooling and practices is so weird to me. Why not just try and see? The fast feedback loop allow testing all kind of weird theories in a matter of 30m-1h during normal working sessions, most results are obvious

The configuration and workflow space is big, and exploring it isn't fun for most people.

Re: Do agents.md files help coding agents?

#20
post #11

The tweet misses the conclusion from the paper that handcrafted AGENTS.md might help. To me its no surprise that 100% vibed AGENTS.md are unproductive. Not reviewing your design docs is probably even worse than not reviewing your code? I've seen some AI-generated agents.md which were just plain wrong. No surprise agents perform worse after reading those. I use AGENTS.md to make sure my agents loop effectively (tests,…

> To me its no surprise that 100% vibed AGENTS.md are unproductive.

To me it is! I thought if an AGENTS.md is researched with much effort once, next time reading the brief conclusion would save on effort and time and cost. Would have seemed logical to me. Like a glossary, looking up a manual, getting briefed before starting.

But I accept the research findings, and I have even had bad experiences with an outdated AGENTS.md derailing the agent.

So now I'm trying to keep to the basics, e.g. just a sentence or two saying "use bun instead of npm" only because I've had to manually prompt that too many times.

It's remarkable how good agents are at exploring, and at treating relatively sparse code reads and get a good picture nevertheless.

Post reply on HN