21–30 of 398 posts
This situation reminds me a bit of ergonomic handles design. Designed for a few people, preferred by everyone.
In what way is this a format or standard? It's just markdown in a namespce
It makes no sense and it really needs standardisation. I hope this catches on.
We're in a transition phase today where agents need special guidance to understand a codebase that go beyond what humans need. Before long, I don't think they will. I think we should focus on our own project documentation being comprehensive (e.g. the contents of this AGENTS.md are appropriate to live somewhere in our documentation), but we should always write for humans. The LLM's whole shtick is that it can read an…
This isn't guaranteed. Just like we will never have fully self-driving cars, we likely won't have fully human quality coders.
Right now AI coders are going to be another tool in the tool bucket.
In what way is this a format or standard? It's just markdown in a namespce
You could get this page down to under 100 words by simply having it say "the name of the file LLM agents will look at for instructions on the repo is AGENTS.md; that's it, that's the standard". It's a real problem! Every agent right now has their own weird filename. I love David Crawshaw's sketch.dev, but for reasons passing understanding they choose "dear_llm.md" for theirs.
edit: They're on it. Not everything has to be complex; sometimes somebody just has to do it.
We're in a transition phase today where agents need special guidance to understand a codebase that go beyond what humans need. Before long, I don't think they will. I think we should focus on our own project documentation being comprehensive (e.g. the contents of this AGENTS.md are appropriate to live somewhere in our documentation), but we should always write for humans. The LLM's whole shtick is that it can read an…
We're in a transition phase today where agents need special guidance to understand a codebase that go beyond what humans need. Before long, I don't think they will. I think we should focus on our own project documentation being comprehensive (e.g. the contents of this AGENTS.md are appropriate to live somewhere in our documentation), but we should always write for humans. The LLM's whole shtick is that it can read an…
With Claude code and others, if I put a context file (agent.MD or whatever) in a project subfolder, e.g., something explaining my database model in with the related code, it gets added to the root project context when the agent is using that subfolder.
It sounds to me like this formulation doesn’t support that.
I'm still not convinced that separating README.md and AGENTS.md is a good idea.
I had the same thought as I read this example. Everything in the AGENTS.md file should just be in a good README.md file.
Earlier quoted context omitted.
That draft RFC you mention is superseded by https://agents.md . Now that Amp uses AGENTS.md ( https://x.com/sqs/status/1957945824404729997 ), I made all the former agent file stuff on https://ampcode.com just redirect to https://agents.md .
Gotcha - this is what I had in my history: https://ampcode.com/AGENT.md For me, that gives a 404 with no obvious way to get to https://agents.md , I think either a hyperlink or redirect would be nice to have as well.