Add persistent per-user exclusion for duplicate Copilot instruction files
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
Describe the feature or problem you'd like to solve
Add persistent per-user exclusion for duplicate Copilot instruction files
Proposed solution
Summary:
GitHub Copilot CLI automatically loads supported instruction files such as CLAUDE.md and AGENTS.md . When both contain duplicate or overlapping instructions, Copilot may load the same guidance twice.
The /instructions command can disable one file, but the change applies only to the current Copilot CLI session. There is currently no documented persistent, user-specific ignore list for excluding one repository instruction file without modifying the shared repository.
This would be useful for teams sharing repositories across multiple people and agents, including Copilot, CloudA, and Codex. A per-user configuration option to permanently exclude selected instruction files—without affecting other users or agents—would prevent duplicate instruction loading while preserving the repository structure.
Example prompts or workflows
My Claude.md file just mentions/loads Agents.md. All the instruction gets loaded twice and bloat the context..
Additional context
No response
Contributor 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.
Research direction
The issue does not identify implementation files, tests, or a configuration entry point, so first locate how /instructions stores session exclusions and where user configuration is loaded. Done means a per-user persistent ignore list can exclude selected repository instruction files without changing the repository or affecting other users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100