Bridge OpenCode structured questions (agent blocks, user only sees a warning) #110

Status — still open (reviewed 2026-08-22)

The generic UI path improved in #190: sessions that emit UserInputRequested are now visibly marked as blocked on a question. pi extension dialogs also use that path after #189.

OpenCode still does not bridge its structured-question protocol. On current main (e8a5f1cc), crates/agent/src/opencode.rs:395-399 handles RespondUserInput by emitting “OpenCode structured questions are not yet bridged by this adapter”; no OpenCode question ingress maps to AgentEvent::UserInputRequested.

Required work

• Map OpenCode question notifications to UserInputRequested.
• Translate RespondUserInput back to the correct OpenCode server API, including cancellation and multi-question answers.
• Clear pending questions on turn completion, interrupt, provider exit, and session switch/restart.
• Keep steering documented separately: the current server API still reports active-turn steering as unsupported.

Acceptance criteria

An OpenCode turn can ask, display, answer, cancel, and resume from a structured question without dead-ending, with adapter and timeline-fold regression tests.

Effort: M · Risk: LOW