-
Notifications
You must be signed in to change notification settings - Fork 13.1k
ACP: let hosts answer ask_user and exit_plan_mode #24663
Copy link
Copy link
Labels
area/non-interactiveIssues related to GitHub Actions, SDK, 3P Integrations, Shell Scripting, Command line automationIssues related to GitHub Actions, SDK, 3P Integrations, Shell Scripting, Command line automationpriority/p2Important but can be addressed in a future release.Important but can be addressed in a future release.
Metadata
Metadata
Assignees
Labels
area/non-interactiveIssues related to GitHub Actions, SDK, 3P Integrations, Shell Scripting, Command line automationIssues related to GitHub Actions, SDK, 3P Integrations, Shell Scripting, Command line automationpriority/p2Important but can be addressed in a future release.Important but can be addressed in a future release.
Type
Fields
Give feedbackNo fields configured for Feature.
ACP needs a host-answerable input request for
ask_userandexit_plan_mode.Right now ACP can start sessions, resume them, send prompts, cancel turns, and handle permission flows. But if Gemini CLI needs structured user input, ACP does not give the host a way to answer it. That forces the flow back into the terminal UI.
That is the gap I need closed.
I want Gemini CLI in ACP mode to work like the other controller boundaries I already use:
The host should be able to:
Relevant ACP work I checked first:
This PR is the narrow fix for that gap: #24664
What it adds:
gemini/requestUserInputask_userexit_plan_modeask_userstays disabled in ACP unless the host explicitly opts inexit_plan_modeif it wantsWhat it does not do:
ask_userback on globally in ACP