@iannuttall I use http://AGENTS.md with http://CLAUDE.md as a symlink.

@iannuttall Historically having a single guideline that every major company works to build is better than having a bunch of fragmented ideas around. I think http://AGENTS.md would work the same way

@iannuttall Already tired reminding Claude to look at http://Claude.md to be honest. Can they make him force look at it once in a while?

@iannuttall Makes no difference to me which MD file holds instructions that anthropic model chooses to ignore.

@iannuttall yes! absolutely! i have a symbolic link in my repos between the two so I don't have to maintain both

@iannuttall That's not really deprecation, unless they say so. There's backward compatibility. That's an option. If I were Anthropic I'd just say no, this is how we role.

@iannuttall Yeah, I use both CC and Codex so I have sync the two files, unecessary

@iannuttall I think it’s a fair approach to standardize but there could be an argument I guess for specific wording that directly speaks to Claude as an agent that may make no sense to other agents

@iannuttall migrating between formats is a production nightmare supporting both http://CLAUDE.md and http://AGENTS.md doubles your context overhead and creates edge cases you never tested I'd standardize on one but the migration path will surface bugs you didn't know existed

@iannuttall Here is my http://CLAUDE.md # http://CLAUDE.md — Agent Notes This repository uses `http://AGENTS.md` as the single source of truth for all contributor and agent guidelines. - Start here: `http://AGENTS.md` - Agent-specific instructions: none at this

@iannuttall I like what Google team response was to this - IIRC they are not adopting it initially because it can create messy experience

@iannuttall this cant be a real post from a software engineer

@iannuttall Yeah. Should be a Type-C cable moment.

@iannuttall It feels like a branding thing more than a technical one. .md implies a static document, while agents are supposed to be dynamic. But users will call it whatever they want regardless of the official filename.

@iannuttall search and replace would solve this they just don't want to

@iannuttall Yes. Because it doesn’t follow the .md anyways.

@iannuttall Not directly on point but people seem to be really liking this: includes a robust setup, session-to-session handoff protocols, and even a live session timer https://github.com/marchoag/Cl...

@iannuttall Sym link if you need this functionality

@iannuttall maybe they wanna add the friction of swapping off claude code

@iannuttall Probably, but I doubt they will.

@iannuttall actually: if http://CLAUDE.md exists and http://AGENTS.md not exists: copy http://CLAUDE.md http://AGENTS.md

@iannuttall Standardization would help to make codebases less bloated. But I feel like we'll also need more agent-specific blocks within the http://AGENTS.md because it wouldn't be a surprise if these agents built specific capabilities others don't offer. And then, the question

@iannuttall might help

@iannuttall I think taskmaster and agentsmd should be in every project

@iannuttall I wish

@iannuttall does cc really follows .md?

@iannuttall I don't really think so. We could have a future where both can be useful.

@iannuttall Yes 👍

@iannuttall Yes

@iannuttall Yeah, hopefully they will adopt this standard!

@iannuttall markdown is markdown

@iannuttall honestly think http://CLAUDE.md gives more flexibility for individual workflows vs forcing everyone into one standard some devs want lightweight configs, others need complex setups. http://AGENTS.md feels too rigid for the variety of use cases out there maybe

@iannuttall 💯

@iannuttall Yes, should be a straightforward change ?

@iannuttall good idea

@iannuttall I like a claude having a separate one tbh The vibes are different between agents