fix: restore CLAUDE.md importing AGENTS.md - #39
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Restores a
CLAUDE.mdthat importsAGENTS.md. Without it, Claude Code loads no projectinstructions for this repo.
The rename to
AGENTS.mdwas made on the belief that Claude Code discoversAGENTS.mdnatively.It does not. The documentation is explicit:
The test that appeared to show otherwise was invalid: it ran with file tools available, so the model
simply read
AGENTS.mdoff disk rather than receiving it as loaded context. Re-run with file toolsdenied, a directory containing only
AGENTS.mdreports the instructions are not in context,while a real
CLAUDE.mdcontrol reports them correctly.Changes
Adds a one-line
CLAUDE.md:AGENTS.mdremains the single home of the content — this is an import, not a copy, so the twocannot drift. Claude Code expands it at session start.
Why an import rather than a symlink
Both work — each was verified with file tools denied. The import is preferred because a symlink
requires Administrator privileges or Developer Mode on Windows; without them the checkout gets a
plain text file containing the target path, which loads as garbage. The import is also the form the
documentation recommends, and it leaves room to append Claude-specific instructions below it later.
Part of modern-python/.github#51.