If you think I'm wrong, and these arguments have nothing to do with it, just tell us what explains Claude not supporting AGENTS.md.
Was it such a grand engineering challenge? Too many 'legacy' projects relying on both AGENTS.md/CLAUDE.md and that has recently changed?
I've made clear my belief on the reason behind it - branding decisions outweighing utility.
Add something to the thread by sharing your version of a 'more likely' decision process that led to the choice to only now support it.
I don’t disagree with anything you say, I just don’t think AGENTS.md ever was a big deal, just a small annoyance
> Our reasoning for this was that we don't think that model families are interchangeable and the system prompt can have a big impact on performance.
They don't even allow alternative harnesses on their subscription model. (But they do allow a agent-sdk that can pretend to be a generic compatible endpoint the alternative harnesses can use).
If you like your stuff overengineered, gated, and over-priced then by all means.
Its not even wrong from Anthropic because it's the path to most profit.
I'll take the opinion of people who have strong opinions about mild inconveniences.
Between my goals and Anthropic's bottom line, i want my goal to win out without needless inconveniences.