MoonshotAI / MoonshotAI/kimi-code

VS Code: AskUserQuestion with multiple questions renders only the first, remaining questions silently dropped

Open
#1,880 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
7.5k
Forks
1.2k
Avg merge
11h 53m
Merged PRs (30d)
350

Description

What version of Kimi Code is running?

VS Code extension moonshot-ai.kimi-code 0.6.3 (win32-x64). The kimi CLI is not installed standalone on this machine, so no kimi --version output is available — the extension is the host.

Which open platform/subscription were you using?

Kimi Code account login (filed via gh on behalf of the user; exact plan not captured)

Which model were you using?

Model-independent — this is a host UI issue in the question-elicitation flow.

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

When the agent calls the built-in AskUserQuestion tool with multiple questions in one call (the tool schema allows 1–4 questions), the VS Code extension only renders the first question. There is no UI indication that further questions exist — no queue, no pagination, no notification.

After the user answers question 1, the interaction closes immediately and the tool result returned to the agent contains only the first question's answer; questions 2–4 are silently dropped. From the agent's perspective the result looks like the user simply skipped the remaining questions, so agents cannot reliably use multi-question calls in VS Code.

Reproduced 3 out of 3 times in a single session (calls with 2 and 4 questions; each time only question 1 rendered and only its answer was returned).

What steps can reproduce the bug?
  1. Open Kimi Code in the VS Code extension.
  2. Have the agent emit one AskUserQuestion tool call with multiple questions, e.g. ask: "use AskUserQuestion to ask me 4 questions in a single call".
  3. Observe: only question 1 is displayed. Answering it closes the flow. The tool result contains only {"answers": {"<question 1 text>": "<chosen label>"}} — questions 2–4 never appear anywhere and their answers are absent from the result.
What is the expected behavior?

All questions of a multi-question call are presented to the user (sequentially or grouped), and each answer (or an explicit dismissal) is returned to the agent — matching the documented tool contract of 1–4 questions per call: https://www.kimi.com/code/docs/en/kimi-code-cli/reference/tools.html

At minimum, if the host can only present one question, it should indicate that additional questions were dropped rather than silently discarding them.

Additional information

Possible root cause: per the ACP capability docs, question elicitation and tool approval share a single channel (session/request_permission — "shared channel for tool approval and question elicitation", https://www.kimi.com/code/docs/en/kimi-code-cli/reference/kimi-acp.html). ACP permission requests model a single prompt with options, so a multi-question AskUserQuestion call may be getting flattened to its first question when adapted to that shape.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the VS Code extension's AskUserQuestion handling and trace how it adapts requests to the ACP session/request_permission channel. Reproduce calls containing 2 and 4 questions, then verify that all questions are presented and their answers or dismissals reach the tool result, or that dropped questions are explicitly reported.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.