diff options
| author | Igor Soarez <igor@soarez.org> | 2026-09-28 12:52:44 +0300 |
|---|---|---|
| committer | Igor Soarez <igor@soarez.org> | 2026-09-28 12:53:00 +0300 |
| commit | 7fc9494ac2b7d905cebff10ff5b8be5a3de80403 (patch) | |
| tree | 835eeafa5436d836d0e2183c9cd76d602deaf280 /bin | |
| parent | cbbc0cb5951960ed62bf9dda0195c168f61d3dc1 (diff) | |
AGENTS.md is the file; CLAUDE.md imports it
Every agent here except Claude Code reads AGENTS.md -- pi, codex, and aider now
that its read: says so. The vendor-neutral name was the symlink and the
Claude-specific one the real file, with a header saying the file was guidance
"to Claude Code". Swapped, keeping history on the real file through git mv.
Claude Code has read AGENTS.md directly since v2.1.277 and the machine this was
done on is newer, so the obvious move was to delete CLAUDE.md. Checking the
other machines first was worth it: four were on versions between 2.1.158 and
2.1.263, and a session on any of them would have found no instructions at all.
So CLAUDE.md stays as one line, `@AGENTS.md`, which the documentation endorses
for exactly this case and which -- unlike the symlink it replaces -- works on
Windows and does not trip Claude Code's refusal to write through a symlink. The
header says to delete it once every machine is current.
Diffstat (limited to 'bin')
| -rwxr-xr-x | bin/dot-request | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/bin/dot-request b/bin/dot-request index a34fe46..c68418e 100755 --- a/bin/dot-request +++ b/bin/dot-request @@ -4,7 +4,7 @@ # # A checkout cloned over https cannot publish anything: a change made on such a # machine is lost at the next pull. So the change is written out, signed, and -# handed to whoever can apply it -- see "Can this machine push?" in CLAUDE.md. +# handed to whoever can apply it -- see "Can this machine push?" in AGENTS.md. # # dot-request --key ~/.config/dot/inbox-key < request.md # some-agent-writing-a-request | dot-request --key ~/.config/dot/inbox-key @@ -14,7 +14,7 @@ # description of it, why, and how to verify it. # # It posts to the request inbox, which is a public endpoint and named here on -# purpose -- see "Can this machine push?" in CLAUDE.md. Reaching it proves +# purpose -- see "Can this machine push?" in AGENTS.md. Reaching it proves # nothing on its own: a request is stored only if it carries a signature from a # key authorised for that inbox. Set DOT_REQUEST_URL to point somewhere else # when testing. |