Repository navigation
ACP: support elicitation for V2 forms and questions #38121
Description
Summary
Add ACP elicitation support in V2 by translating session forms/questions into unstable_createElicitation requests when the connected ACP client advertises support.
Today, all session forms are auto-cancelled in the ACP path, so an agent cannot collect structured input from a capable client.
Expected behavior
- Detect whether the ACP client supports elicitation.
- Translate V2 session forms/questions into
unstable_createElicitationrequests when supported. - Return the client's submitted or cancelled result to the waiting session flow.
- Preserve the current auto-cancel fallback when elicitation is unsupported.
- Cover supported, cancelled, and unsupported-client paths with tests.
Requested by: @nexxeln (Shoubhit Dash via Slack)
Activity
fix(opencode): bridge question tool to ACP elicitation
zeroliu commentedon Sep 22, 2026
Adding a client-side data point. Obsidian Copilot is an ACP client that is adding
elicitation.formsupport now.codex-acpalready sends Codex'srequest_user_inputaselicitation/create, so our users will see Codex questions inline, while OpenCode'squestiontool is cancelled over ACP (packages/cli/src/acp/event.ts,form.created). The model's question is lost and the turn endscancelled.Elicitation is stable in the ACP schema, and
createElicitationis stable from@agentclientprotocol/sdk1.4.0. #38311 appears to implement this issue but was closed by the stale-PR bot without a review. Could it be reopened or rebased? We're happy to test it against our client.nexxeln commentedon Oct 6, 2026
Fixed on v2. #52511 sends V2 question forms to clients that advertise elicitation.form as ACP elicitation requests and returns the answers to the session, and #52740 cancels questions a client can't show while letting the model continue.