Describe the feature or problem you'd like to solve
Copilot CLI does not discover custom agents from a subdirectory’s .github/agents folder in monorepos, even when CLI is started from that subdirectory. The same agent works in VS Code and other CLI customizations (prompts, instructions, skills) in that subdirectory can still be recognized.
Proposed solution
Allow Copilot CLI to discover custom agents from the current working directory’s .github/agents folder, not only from the Git repository root. This would make custom agent behavior more consistent with prompts, instructions, and skills, improve monorepo support, and reduce confusion when VS Code and Copilot CLI behave differently.
Example prompts or workflows
root - .git
- app1
- .github
- agents
- app2
- .github
- agents
Additional context
No response
Describe the feature or problem you'd like to solve
Copilot CLI does not discover custom agents from a subdirectory’s .github/agents folder in monorepos, even when CLI is started from that subdirectory. The same agent works in VS Code and other CLI customizations (prompts, instructions, skills) in that subdirectory can still be recognized.
Proposed solution
Allow Copilot CLI to discover custom agents from the current working directory’s .github/agents folder, not only from the Git repository root. This would make custom agent behavior more consistent with prompts, instructions, and skills, improve monorepo support, and reduce confusion when VS Code and Copilot CLI behave differently.
Example prompts or workflows
root - .git
- app1
- .github
- agents
- app2
- .github
- agents
Additional context
No response