Development record
Evaluate whether CLAUDE.md can be removed safely now that Claude Code reads AGENTS.md natively. Today CLAUDE.md duplicates the AGENTS.md router. Check every place that relies on CLAUDE.md being present: the harness's own loading in the main session, sub-agents and plugin contexts; abcd's ahoy/prepare-this-repo scaffolding and lint rules that expect CLAUDE.md as a bridge; docs that name it; and managed repos abcd sets up. Only remove it if every consumer reads AGENTS.md.
Evaluate whether CLAUDE.md can be removed safely now that Claude Code reads AGENTS.md natively. Today CLAUDE.md duplicates the AGENTS.md router. Check every place that relies on CLAUDE.md being present: the harness's own loading in the main session, sub-agents and plugin contexts; abcd's ahoy/prepare-this-repo scaffolding and lint rules that expect CLAUDE.md as a bridge; docs that name it; and managed repos abcd sets up. Only remove it if every consumer reads AGENTS.md.
Grounds
Promoted to itd-2610030814013772 on 2026-10-03 without recorded grounds: no pursued conjecture was stated at promotion. The conjecture is put to the product thinker at the draft's planning interview (its Mechanism, Q6).
- pursued: we expect a fresh session in abcd's own checkout to load AGENTS.md with no CLAUDE.md present, so the Windows-clone failure of the links ends; a fresh session that cannot name the canary word, or either link restored at the root, would show it wrong
Frontmatter
| id | iss-2609291925136841 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2609291925136841-evaluate-whether-claude-md-can-be.md
open on GitHub ↗ · commit history ↗
References1
- itd-2610030814013772abcd's projects keep one conventions file, AGENTS.md, and Claude Code reads it directlyrelated
mentions1
- spc-2610031156364295evaluate-whether-claude-md-can-be-removed-safely-now-that