- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
Which makes sense, if you want some standards across contributions. Setting aside that agent assisted contribution itself is questionable, as long as it is happening, a universal agents file is probably helpful.
I don’t get why agents.MD needs to be committed. It feels a bit like committing IDE settings, everyone is going to have slightly different preferences, so its better to just have everyone do their own thing. If anything, I prefer to .gitignore itso it doesnt get accidentally committed.
For agents (semi-autonomous) I think it’s more similar to introductory developer docs. Which are usually committed.
Like formatters and git ignore configuration, some agent instructions are personal and those should not be commited. But some are worth sharing. Having formatter config in a repo is not uncommon. And in this case the file is only a link to the readme, so the agent reads the contrib guidelines.
I’m on board with committing formatter config, because thats deterministic and really should be shared amongst a team.
I don’t get why the agent needs to have the contrib guidelines, it should be a human doing the actual contrib part, so its just a waste of tokens for the LLM to read it?
I don’t get why the agent needs to have the contrib guidelines, it should be a human doing the actual contrib part, so its just a waste of tokens for the LLM to read it?
Why would you want to waste the tokens required to generate a subpar response that will either require the user to undo a potentially significant portion of what was generated, or you’ll end up using more tokens while the operator tries to get the AI to obey the standard (before they inevitably tell the stupid thing to follow the guide themselves later, anyway)?
At least for the specific example given, I want developers to do the commit part themselves, so if their LLM is doing any part of that, its already a mistake IMO.
I had a very quick look at the AI agent guidelines, and nothing about them strikes me as overly burdensome for a human to fix up. So I’d rather just do that myself (if I were a kernel dev).
My main objection is forcing it on developers, it should be up to each dev to configure and manage their own agent. Making it a suggestion is fine, just don’t commit it. Also, if developers are using local hosted models, then context may be quite limited, so wasting it on an Agents.MD maybe be unideal.
Waste of tokens for the agent to make changes that the human then changes to comply with contrib guidelines. Potentially a smaller number used to read in some guidelines and get closer to correct in the first place.
A contributor still has global config for their personal preferences. It makes sense to me, anyway. My biggest issue is it’s not deterministic. Someone else could have a version that works better or uses fewer tokens for the same thing.
At work we commit the whole
.claudefolder, though we carve out some space for personal agents and skills.
Everywhere I go I started leaving AGENTS.md files. I feel like the future needs some reliability and stability as LLMs help us improve everything we do. So if your agent replies with a bunch of shit emojis or an ASCII art of a beautiful veiny dick then you can thank this guy and is AGENTS.md files. You’re welcome.
Agents md file doesn’t actually do anything except using more tokens https://arxiv.org/pdf/2602.11988
I feel like you either didn’t read your article or didn’t read the post article
BSD here i come.
This is being proposed so that the bot doesn’t have to read the entire README file. Humans are supposed to do it but the bot replacing them does not. Makes sense to me.
Surely this will improve code quality for the single most important piece of software in existence today.
We’re gonna have to end up using TempleOS to avoid this AI bullshit arent we.
Or one might try BSD before installing TempleOS… BSD might just do the trick.
BSD is too usable. will have AI in it before long.
As they should. It’ll make better ai commits and reduce time needed for review.
There should be one that bans ai from the repo
Ok
