Describe the bug
In copilot --acp, the task tool cannot start any custom agent from ~/.copilot/agents. The call fails before the agent runs:
host interaction call failed: Error: Unsupported native sessions host effect 'custom_agent_prompt'
Built-in agents such as explore still work in the same session. The same custom agent works in copilot -p, and in copilot --acp 1.0.88 and earlier.
| Version |
Mode |
Custom agent launch |
| 1.0.86, 1.0.87-0, 1.0.88 |
--acp |
Works |
| 1.0.89 |
--acp |
Fails |
| 1.0.90 |
--acp |
Fails |
| 1.0.89 |
-p |
Works |
| 1.0.89, 1.0.90 |
--acp, built-in explore |
Works |
Affected version
GitHub Copilot CLI 1.0.89 and 1.0.90
Steps to reproduce the behavior
- Create
%USERPROFILE%\.copilot\agents\my-agent.agent.md:
---
name: my-agent
description: Test agent
---
Reply with exactly: LAUNCHED
- Start
copilot --acp and send initialize, then session/new.
- Send
session/prompt asking the model to call the task tool once with agent_type: "my-agent".
- The
tool_call_update for the task call has status failed and the error above.
- Repeat step 3 with
agent_type: "explore". It completes.
- Repeat with
copilot --acp --prefer-version 1.0.88. my-agent completes.
Expected behavior
The custom agent runs and returns its result, as it does in 1.0.88 and in copilot -p.
Additional context
- Windows 11, x86_64. ACP over stdio from a Node client, no terminal emulator involved.
- Possible cause, an inference from reading the bundled JavaScript and not confirmed: before 1.0.89, ACP sessions routed host effects to
runNativeSessionHostEffect, which handles custom_agent_prompt. From 1.0.89, ACP goes through the native sessions server, and its clientSession/hostEffect path calls runServerHostEffect, which only handles server effects and throws for custom_agent_prompt. The version results above are tested.
- Workaround:
copilot --acp --prefer-version 1.0.88, when that version is cached.
Describe the bug
In
copilot --acp, the task tool cannot start any custom agent from~/.copilot/agents. The call fails before the agent runs:Built-in agents such as
explorestill work in the same session. The same custom agent works incopilot -p, and incopilot --acp1.0.88 and earlier.--acp--acp--acp-p--acp, built-inexploreAffected version
GitHub Copilot CLI 1.0.89 and 1.0.90
Steps to reproduce the behavior
%USERPROFILE%\.copilot\agents\my-agent.agent.md:copilot --acpand sendinitialize, thensession/new.session/promptasking the model to call the task tool once withagent_type: "my-agent".tool_call_updatefor the task call has statusfailedand the error above.agent_type: "explore". It completes.copilot --acp --prefer-version 1.0.88.my-agentcompletes.Expected behavior
The custom agent runs and returns its result, as it does in 1.0.88 and in
copilot -p.Additional context
runNativeSessionHostEffect, which handlescustom_agent_prompt. From 1.0.89, ACP goes through the native sessions server, and itsclientSession/hostEffectpath callsrunServerHostEffect, which only handles server effects and throws forcustom_agent_prompt. The version results above are tested.copilot --acp --prefer-version 1.0.88, when that version is cached.