You can save a tool call by just making it a symlink
replyYou can also use @AGENTS.md which automatically concatenates the files
replyThis is the way.
replyMine does too because, while I use Codex, my non-technical co-founder uses Claude. I find Claude still will randomly ignore instructions in there. Basic things like how to name a PR or what to put in a PR description.
replyMy experience is that what you're suggesting isn't a perfect solution.
Are you saying this wouldn’t happen if the file had a different name? Or just that codex is better at instruction following.
replyNo. I'm saying that the pattern of having one instruction file that just says "read this other file" doesn't seem to work well. Having a CLAUDE.md that just says "Read AGENTS.md" resulted in Claude randomly not following the rules. We tried the other way and it didn't seem like it was any better, but also, given that AGENTS.md is the standard everywhere except for Claude Code, I don't really want CLAUDE.md to be the source of truth
replyAt the current price for SSDs even a pointless symlink becomes waste...
replyA high quality 1TB NVME SSD costs 164€ on Amazon right now.
replyFor a 10 byte symlink, that costs one billionth of a euro.
This is like worrying about the money you lose when part of a glass of tap water evaporates.
Are you serious? A symlink is probably one of the smallest files you can possibly generate.
replywell I generally agree, pretty much every other harness supports looking for the various alternatives and uses them
replyI see this obstinance as an intent signal and one of the smaller bullet points I have for avoiding Ant