Describe the bug
When asked to locate a file like ado-mcp.env, the agent searched only the repo directory and then escalated to a drive-root scan
— skipping $HOME/.copilot/ entirely, despite the documentation explicitly listing it as a profile-level config directory.
The agent should apply file-type reasoning first (.env + ado-mcp prefix → MCP config → ~/.copilot/), check the documented lookup
order (repo → repo root → $HOME/.copilot/), and only ask the user if all three fail — never scan from drive root.
This is a tool-first, reasoning-last anti-pattern that should be corrected in the agent's lookup heuristics.
bug-conversation.txt
Affected version
GitHub Copilot CLI 1.0.21.
Steps to reproduce the behavior
- save ado mcp details in ~/.copilot/ado-mcp.env
- go to your repo folder
- ask: create pull request
Expected behavior
it should have look into ~/.copilot folder for env file
Additional context
Operating system: windows 11
processor : x86_64
terminal: windows terminal
bash: git bash
Describe the bug
When asked to locate a file like ado-mcp.env, the agent searched only the repo directory and then escalated to a drive-root scan
— skipping $HOME/.copilot/ entirely, despite the documentation explicitly listing it as a profile-level config directory.
The agent should apply file-type reasoning first (.env + ado-mcp prefix → MCP config → ~/.copilot/), check the documented lookup
order (repo → repo root → $HOME/.copilot/), and only ask the user if all three fail — never scan from drive root.
This is a tool-first, reasoning-last anti-pattern that should be corrected in the agent's lookup heuristics.
bug-conversation.txt
Affected version
GitHub Copilot CLI 1.0.21.
Steps to reproduce the behavior
Expected behavior
it should have look into ~/.copilot folder for env file
Additional context
Operating system: windows 11
processor : x86_64
terminal: windows terminal
bash: git bash