-
Notifications
You must be signed in to change notification settings - Fork 1.4k
--agent <agent name> does not work with --plugin-dir <dir> -p <prompt> #2795
Copy link
Copy link
Open
Labels
area:agentsSub-agents, fleet, autopilot, plan mode, background agents, and custom agentsSub-agents, fleet, autopilot, plan mode, background agents, and custom agentsarea:non-interactiveNon-interactive mode (-p), CI/CD, ACP protocol, and headless automationNon-interactive mode (-p), CI/CD, ACP protocol, and headless automationarea:pluginsPlugin system, marketplace, hooks, skills, extensions, and custom agentsPlugin system, marketplace, hooks, skills, extensions, and custom agents
Metadata
Metadata
Assignees
Labels
area:agentsSub-agents, fleet, autopilot, plan mode, background agents, and custom agentsSub-agents, fleet, autopilot, plan mode, background agents, and custom agentsarea:non-interactiveNon-interactive mode (-p), CI/CD, ACP protocol, and headless automationNon-interactive mode (-p), CI/CD, ACP protocol, and headless automationarea:pluginsPlugin system, marketplace, hooks, skills, extensions, and custom agentsPlugin system, marketplace, hooks, skills, extensions, and custom agents
Type
Fields
Give feedbackNo fields configured for Bug.
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