SDK cannot handle `question` tool interaction (no way to respond to tool calls in serve mode)

[ZYT20001]

Description

Problem

When using OpenCode via SDK (not CLI), there is no way to handle or respond to the question tool call triggered by the model.

In my setup, I built a custom frontend (web UI) and communicate with OpenCode through the SDK + backend service. However:

• The model frequently triggers the question tool
• The server enters a waiting state for user input
• But the SDK does NOT expose any API to:
  • intercept the question tool call
  • provide the answer programmatically
  • continue the execution loop

This causes the request to hang indefinitely.

---

Expected Behavior

There should be a way in SDK / serve mode to:

1. Detect when a question tool is triggered
2. Retrieve the question payload (prompt, metadata, etc.)
3. Send back the user's answer programmatically
4. Resume the execution

Example (pseudo API):

client.onToolCall((tool) => {
  if (tool.name === "question") {
    return {
      answer: "user input from my UI"
    }
  }
})

### Plugins

_No response_

### OpenCode version

1.3.2

### Steps to reproduce

## CLI vs SDK Behavior

CLI:
- `question` is displayed
- user can input answer
- execution continues

SDK:
- `question` is triggered internally
- no way to respond
- execution hangs

This indicates the interaction layer exists in CLI but is not exposed in SDK.

### Screenshot and/or share link

_No response_

### Operating System

windows

### Terminal

_No response_

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• [FEATURE] Expose Question.ask for API/SDK to use #19140: Feature request to expose Question.ask for API/SDK — directly addresses the same missing SDK functionality you're describing
• Question tool hangs in ACP mode #17920: Same hanging behavior with the question tool, in ACP mode — same root cause (no handler forwards question.asked events to external clients)

If your issue is not covered by either of those, please add clarifying details to differentiate.

[theredbluepill]

This issue is indeed so annoying..

[theredbluepill]

Can try custom tool:

import { tool } from "@opencode-ai/plugin"

export const ask_user = tool({
  description:
    "Ask the user a question with multiple-choice options. " +
    "This tool returns IMMEDIATELY — it does NOT block or wait for the answer. " +
    "The playground UI will show an interactive selection banner. " +
    "The user's answer will arrive as the next message in the conversation. " +
    "After calling this tool, STOP and wait for the user's reply before continuing.",
  args: {
    questions: tool.schema
      .array(
        tool.schema.object({
          id: tool.schema.string().describe("Unique question identifier"),
          prompt: tool.schema
            .string()
            .describe("The question text to display"),
          options: tool.schema
            .array(
              tool.schema.object({
                id: tool.schema.string().describe("Option identifier"),
                label: tool.schema.string().describe("Option display text"),
              }),
            )
            .describe("List of choices the user can pick from"),
          allow_multiple: tool.schema
            .boolean()
            .optional()
            .describe("If true, user can select multiple options"),
        }),
      )
      .describe("One or more questions to ask the user"),
  },
  async execute(args) {
    const summary = args.questions
      .map((q) => `${q.prompt} (${q.options.length} options)`)
      .join("; ")
    return `Asked the user: ${summary}. Waiting for their reply in the next message.`
  },
})

[rekram1-node]

Automated: closing question issues.

GitHub Issues are for bug reports and feature requests only — questions / support are no longer tracked here.

• For help & questions: https://discord.gg/opencode
• Billing issues with Opencode Go / Zen: help@anoma.ly

If this is a bug or feature request, please open a new issue with the appropriate template.