Comment by ValentineC
8 hours ago
My CLAUDE.md is just:
@AGENTS.md
And Claude processes it just fine.
(I see that it's a common workaround, and there's a comment in the above link saying just this: https://github.com/anthropics/claude-code/issues/6235#issuec...)
It's a hassle having to add it to every repo that I use Claude with though, and I often use other models and harnesses too for the more trivial tasks.
I beg people to learn what symlinks are. The fact that "put @AGENTS.md in there" is a "common workaround" shows why programmers (good ones at least) are not going anywhere soon.
I used to use a symlink but was concerned that Claude might see the presence of an "AGENTS.md" file (in e.g, a "List Files" tool call output or from a direct `ls`), be curious and attempt to read it directly (not knowing that it's the same as the "CLAUDE.md" file auto-injected by the harness), and essentially double the token impact / context bloat. Indeed, I did some local experimentation and noticed this was the case, which is why I switched to the explicit "@AGENTS.md" approach.
So perhaps there's no need to be rude about it :)
Good programmers know symlinks are not portable
Neither are line endings. But like line endings, I just put it into git and get over it.
One bonus to this approach is that I can add Claude Code-specific stuff in there, that I wouldn't need for other harnesses.
Symlinks aren’t portable.
Symlinks are a pain if you're on Windows, I'd rather not bother with them.
I never had any issues with them. And they fixed my problems in a good way.
>Symlinks are a pain if you're on Windows
How so?
I'm pretty sure some agent harnesses read both files when present, so this @ "aliasing" is more token efficient.