Repository navigation
Mode changes does not work with ACP #2942
Description
Describe the bug
I have found two bugs related to modes in ACP:
-
The agent cannot leave plan mode. Once we start plan mode and then plan is done, it should propose to execute the plan and swap modes
-
Autopilot mode has no effect. I am unsure if this is related to the separation between autopilot vs /allow-all, but it still always asks for permission. We may need autopilot to automatically enable /allow-all for ACP
Affected version
1.0.35
Steps to reproduce the behavior
I was able to reproduce those bugs both in Zed and Tidewave.
- Enter plan mode, ask it to plan and execute the plan. You see no tool request arrives.
- Simply choose autopilot and ask it to make changes and run commands. You see it will request tool permissions.
Glad to provide any more info. :)
Expected behavior
No response
Additional context
No response
Activity
EL-PS commentedon Apr 27, 2026
I encountered a similar issue in the copilot-chat integrated to VSCode, there agent tell me explicitely that it's still in plan (or ask mode) and cannot start implementing (same happened when I manually switched mode).
patniko commentedon Oct 26, 2026
Thanks for the report. Both parts have been addressed: switching an ACP session to autopilot now enables allow-all permissions before the mode change completes, so autopilot no longer prompts for tool, path or URL access (Copilot CLI v1.0.52), and ACP clients receive live mode updates (v1.0.81), so when the agent finishes planning and you approve its request to exit plan mode, the session leaves plan mode and the client gets a
current_mode_update. A further fix to the ordering of ACP mode and permission changes is merged and will ship in v1.0.104. If either problem still reproduces in Zed or Tidewave on the latest version, please reopen with your CLI version.Triaged as part of a Copilot SDK backlog review, with help from GitHub Copilot.