Describe the bug
When I use --agent with --plugin-dir -p , it starts scanning the .copilot or .github directory for .
Though this agent is present in the plugin-dir, copilot is not able to find it.
If I don't pass -p , the copilot TUI opens and I can see the agent selected.
I am using the version 1.0.31 (latest)
Affected version
No response
Steps to reproduce the behavior
- Download a plugin to a directory, with a "agent/.agent.md"
- pass the same agent name as "copilot --agent --plugin-dir " -> You will see the TUI showing "agent name" selected
- Now pass with -p switch "copilot --agent --plugin-dir -p 'hi' " -> This will error out saying the agent is not available
Expected behavior
(With and without -p) and with --plugin-dir and with --agent, copilot should be able to find the right agent
Additional context
No response
Describe the bug
When I use --agent with --plugin-dir -p , it starts scanning the .copilot or .github directory for .
Though this agent is present in the plugin-dir, copilot is not able to find it.
If I don't pass -p , the copilot TUI opens and I can see the agent selected.
I am using the version 1.0.31 (latest)
Affected version
No response
Steps to reproduce the behavior
Expected behavior
(With and without -p) and with --plugin-dir and with --agent, copilot should be able to find the right agent
Additional context
No response