Troubleshooting guide · GitHub Docs checked Nov 3, 2026
What to check when Copilot CLI seems to ignore instructions
When Copilot CLI appears to ignore repository instructions, first confirm the active repository and instruction discovery with `/instructions`; then check file scope, conflicts, and whether the current session was refreshed. A public report is one qualitative example, not proof of a current general regression.
Why might Copilot CLI seem to ignore `.github/copilot-instructions.md`?
GitHub documents that Copilot CLI automatically includes repository-wide instructions while working inside that repository. First check that the file is at the repository root under `.github/`, that the CLI is working in the intended repository, and that the instruction is clear and relevant to the current task. A GitHub Community discussion from July 2026 reports one user's instructions being followed inconsistently; it does not establish a general or current regression.
How can I see which instruction files Copilot CLI discovered?
In an interactive Copilot CLI session, run `/instructions`. GitHub says this lists files discovered for the current session and lets you enable or disable individual files. Check that the expected repository file appears and is enabled. User-level locations can also change when `COPILOT_HOME` is set.
What repository paths does Copilot CLI check?
GitHub documents repository and agent instruction discovery from the repository root, the current working directory, intermediate directories between them, and directories nested in the path of a file being worked on. The repository-wide file is `.github/copilot-instructions.md`. Path-specific files use `.github/instructions/NAME.instructions.md` and an `applyTo` glob; they apply only when that glob matches a file the CLI is working on.
Do changes to an instruction file affect an open session?
GitHub says changes to custom-instruction files are not immediately available in active CLI sessions. Exit and resume the session, or start a new session with `/new`, before testing the change again.
What if multiple instruction files disagree?
GitHub documents that applicable user-level, repository-wide, and agent instruction files are combined, and says there is no general precedence order between them. Look for contradictory instructions, duplicate rules, or a path-specific rule that changes the expected behavior. Keep the test case focused on one rule.
How can I tell whether the file loaded or the model simply did not follow it?
Use `/instructions` to inspect the discovered and enabled file list, then make a minimal test in a fresh session: add one harmless, unmistakable instruction and ask for a task that directly exercises it. Record the CLI version, operating system, working directory, file path, model, and prompt. A failed behavior test does not alone prove the file was not loaded; distinguish discovery from instruction-following.
Does this guide prove Copilot CLI has an instructions regression?
No. The linked discussion is one user's report and includes other users' replies; it does not verify a root cause or measure how often instructions fail. The checks here are based on GitHub's current documented discovery and session behavior, not a reproduction of that report.
Sources
- GitHub Docs: Adding custom instructions for Copilot CLI · discovery, scope, and session refresh · checked Nov 3, 2026
- GitHub Docs: Support for different types of custom instructions · surface support matrix · checked Nov 3, 2026
- GitHub Community discussion #202257: Copilot CLI instructions reported as inconsistently followed · July 18, 2026 · qualitative report