Skip to content

ACP: let hosts answer ask_user and exit_plan_mode #24663

Closed

Description

@benjaminwestern

ACP needs a host-answerable input request for ask_user and exit_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:

  • Codex app-server
  • Claude Agent SDK

The host should be able to:

  • receive the input request
  • show it in its own UI
  • send the answer back
  • continue the same turn

Relevant ACP work I checked first:

This PR is the narrow fix for that gap: #24664

What it adds:

  • an opt-in ACP extension: gemini/requestUserInput
  • host-answerable handling for ask_user
  • host-answerable handling for exit_plan_mode
  • ask_user stays disabled in ACP unless the host explicitly opts in
  • per-kind support so a host can enable only exit_plan_mode if it wants

What it does not do:

  • add MCP
  • add a second app-server
  • turn ask_user back on globally in ACP

Activity

  1. added
    status/need-triageIssues that need to be triaged by the triage automation.
    area/non-interactiveIssues related to GitHub Actions, SDK, 3P Integrations, Shell Scripting, Command line automation
    on Apr 4, 2026
  2. changed the title [-]feat(acp): support host input requests for ask_user and exit_plan_mode[/-] [+]ACP: let hosts answer ask_user and exit_plan_mode[/+] on Apr 4, 2026
  3. changed the title [-]ACP: let hosts answer ask_user and exit_plan_mode[/-] [+]feat(acp): support host input requests for ask_user and exit_plan_mode[/+] on Apr 4, 2026
  4. changed the title [-]feat(acp): support host input requests for ask_user and exit_plan_mode[/-] [+]ACP: let hosts answer ask_user and exit_plan_mode[/+] on Apr 4, 2026
  5. added
    priority/p2Important but can be addressed in a future release.
    and removed
    status/need-triageIssues that need to be triaged by the triage automation.
    on Apr 10, 2026
  6. Adib234 commented on May 8, 2026

    @Adib234
    Contributor

    Thank you for bringing this to our attention. Right now, our engineering team is focusing all resources on critical system maintenance and core stability. Because of this, we don't have immediate plans to address this specific issue, but we truly appreciate you flagging it for us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/non-interactiveIssues related to GitHub Actions, SDK, 3P Integrations, Shell Scripting, Command line automationpriority/p2Important but can be addressed in a future release.type/feature

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions