Describe the bug
The INSTRUCTIONS path listed by the /help command is as follows:
INSTRUCTIONS READ FROM:
CLAUDE.md
GEMINI.md
AGENTS.md in git root & cwd
.github/instructions/**/*.instructions.md in git root & cwd
.github/copilot-instructions.md
$HOME/.copilot/copilot-instructions.md
COPILOT_CUSTOM_INSTRUCTIONS_DIRS additional directories via env var
The path $HOME/.copilot/instructions/*.instructions.md was omitted. The changelog for version 0.0.412 explicitly mentions: "Support ~/.copilot/instructions/*.instructions.md files for user-level instructions across all repositories," and my testing confirms it is indeed effective: https://github.com/github/copilot-cli/blob/main/changelog.md#00412---2026-02-19
PS: Since VSCode does not support loading $HOME/.copilot/copilot-instructions.md, I created a $HOME/.copilot/instructions/global.instructions.md file with applyTo: '**' and all other content identical. As a result, I now see that $HOME/.copilot/instructions/ is also being loaded in the Copilot CLI. Could this cause the same content to be loaded twice, resulting in wasted context?
Affected version
No response
Steps to reproduce the behavior
No response
Expected behavior
No response
Additional context
No response
Describe the bug
The INSTRUCTIONS path listed by the /help command is as follows:
The path
$HOME/.copilot/instructions/*.instructions.mdwas omitted. The changelog for version 0.0.412 explicitly mentions: "Support ~/.copilot/instructions/*.instructions.md files for user-level instructions across all repositories," and my testing confirms it is indeed effective: https://github.com/github/copilot-cli/blob/main/changelog.md#00412---2026-02-19PS: Since VSCode does not support loading $HOME/.copilot/copilot-instructions.md, I created a $HOME/.copilot/instructions/global.instructions.md file with applyTo: '**' and all other content identical. As a result, I now see that
$HOME/.copilot/instructions/is also being loaded in the Copilot CLI. Could this cause the same content to be loaded twice, resulting in wasted context?Affected version
No response
Steps to reproduce the behavior
No response
Expected behavior
No response
Additional context
No response