repo budget: Copilot profiles get Claude Code's root CLAUDE* rule, so a root AGENTS.md reads off
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 42/100
Research direction
Start in repos/budget.py: the if root_claude: branch of _displaced and the off assignment for a root CLAUDE* file both key on guidance names rather than the guidance.claude_displaces_agents flag that #366 added. Check how repo receipt computes expected and whether it applies budget's rules for every harness. Done when a test with --harness copilot and copilot-review reports a root AGENTS.md as start next to a root CLAUDE.md, and receipt agrees.
Written by the indexing model from the issue text.
Description
repo budget applies Claude Code's root rule to any profile whose guidance names include CLAUDE.md: a root CLAUDE.md, .claude/CLAUDE.md or CLAUDE.local.md turns every AGENTS.md off, with the warning "Claude Code does not read it". copilot.yaml and copilot-review.yaml list CLAUDE.md, so with --harness copilot a tree holding a root AGENTS.md and a root CLAUDE.md reports AGENTS.md as off. Yet copilot.yaml's own notes say Copilot CLI 1.0.91 applied both the root AGENTS.md and the CLAUDE.md.
#366 gates the new same-directory rule on the profile flag guidance.claude_displaces_agents, which only claude-code.yaml sets. The root rule (the if root_claude: branch of _displaced in repos/budget.py, and the off assignment for a root CLAUDE*) predates that PR and still keys on the names. The fix is likely the same gate: a Copilot budget then reads the root AGENTS.md as start, and a test pins it with --harness copilot and copilot-review. Check repo receipt's expected too: it takes off from budget, but it applies budget's rules only for claude-code.
Found while answering https://github.com/intel/dokimi/pull/366#discussion_r4445841674.
- Dominant language
- Python
- Stars
- 9
- Forks
- 9
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 282
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from intel/dokimi
-
Difficulty 4/5 3-5 days Newbie friendliness 18/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
Maintainers usually reply within 1 day
-
eval reference: stamp a digest of the questions file so headroom catches an edit at the same pathOpen
Difficulty 3/5 1-2 days Newbie friendliness 32/100
Maintainers usually reply within 1 day
-
Harbor features unsupported: MCP servers, compose sidecar services, separate verifier environmentOpen
Difficulty 5/5 Over a week Newbie friendliness 12/100
Maintainers usually reply within 1 day
Similar issues
-
ci-rerun: collect.py fails a whole pr-babysit cycle on one transient GitHub 5xx and never retriesOpenfollow-up
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Built-in QUBO fallback applies bitwise xor to floating binary statesPossibly taken @iloveeyjafjalla claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
qboson/kaiwu-pytorch-plugin#1702 ·
Maintainers usually reply within 3 days
-
bug v2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
modelcontextprotocol/python-sdk#3811 ·
Maintainers usually reply within 1 day
-
cost:cheap practicality:seen-in-the-wild severity:medium
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fairagro/m4.2_advanced_middleware_api#620 ·
Maintainers usually reply within 1 day