Short summary
Creating a session in a folder-backed project fails for plugin-provided custom agents. The session-creation flow appears to resolve the agent's unqualified file name instead of its plugin-qualified identifier.
Affected version or release
App v1.1.19/CLI 1.0.84-4
Installation context
Windows desktop installation with user-scoped plugins.
Affected scope: folder-backed local projects, including non-Git folders. The issue has reproduced with agents supplied by multiple plugins, including database-data-management@awesome-copilot.
What happened?
When creating a session in a folder project and selecting a plugin-provided custom agent, session creation fails before the agent starts.
For example, the "MS SQL Database Administrator" agent is defined as ms-sql-dba by the database-data-management@awesome-copilot plugin. It is registered under database-data-management:ms-sql-dba (plugin-qualified identifier), but the session-creation flow attempts to resolve only the unqualified ms-sql-dba identifier.
The resulting error follows this pattern:
Failed to create session: RPC error -32603: Request session.create failed with message: session construction failed: Custom agent 'ms-sql-dba' not found
Steps to reproduce
- Install and enable the database-data-management@awesome-copilot plugin.
- Open or create a folder-backed local project.
- Create a new session for that folder.
- Select the MS SQL Database Administrator custom agent.
- Attempt to create or start the session by entering some text, ex: "What does this agent do?"
- Observe that session construction fails because the unqualified
ms-sql-dba agent ID cannot be found.
Expected behavior
The session should be created and started with the selected plugin-provided custom agent.
The session-creation flow should preserve and resolve the plugin-qualified agent identifier, rather than resolving only the unqualified file name. EX: it should resolve as database-data-management:ms-sql-dba rather than only ms-sql-dba.
Additional context
Temporary workaround:
- Create
%USERPROFILE%\\.copilot\agents\ if it does not already exist.
- Copy the affected agent's .agent.md definition from the installed plugin into that directory using its unqualified file name. EX: copy raw ms-sql-dba.agent.md to
%USERPROFILE%\\.copilot\agents\ms-sql-dba.agent.md.
- Restart the Copilot App.
This makes the unqualified agent name available as a user-level custom agent and allows session creation to succeed.
However, this workaround must be repeated for each affected plugin agent, applies to every local project for the user, and creates copies that can drift from the plugin-provided agent definitions. A platform-level fix to plugin-agent resolution during folder-session creation would remove the need for these copies.
Short summary
Creating a session in a folder-backed project fails for plugin-provided custom agents. The session-creation flow appears to resolve the agent's unqualified file name instead of its plugin-qualified identifier.
Affected version or release
App v1.1.19/CLI 1.0.84-4
Installation context
Windows desktop installation with user-scoped plugins.
Affected scope: folder-backed local projects, including non-Git folders. The issue has reproduced with agents supplied by multiple plugins, including database-data-management@awesome-copilot.
What happened?
When creating a session in a folder project and selecting a plugin-provided custom agent, session creation fails before the agent starts.
For example, the "MS SQL Database Administrator" agent is defined as
ms-sql-dbaby the database-data-management@awesome-copilot plugin. It is registered underdatabase-data-management:ms-sql-dba(plugin-qualified identifier), but the session-creation flow attempts to resolve only the unqualifiedms-sql-dbaidentifier.The resulting error follows this pattern:
Steps to reproduce
ms-sql-dbaagent ID cannot be found.Expected behavior
The session should be created and started with the selected plugin-provided custom agent.
The session-creation flow should preserve and resolve the plugin-qualified agent identifier, rather than resolving only the unqualified file name. EX: it should resolve as
database-data-management:ms-sql-dbarather than onlyms-sql-dba.Additional context
Temporary workaround:
%USERPROFILE%\\.copilot\agents\if it does not already exist.%USERPROFILE%\\.copilot\agents\ms-sql-dba.agent.md.This makes the unqualified agent name available as a user-level custom agent and allows session creation to succeed.
However, this workaround must be repeated for each affected plugin agent, applies to every local project for the user, and creates copies that can drift from the plugin-provided agent definitions. A platform-level fix to plugin-agent resolution during folder-session creation would remove the need for these copies.