fix(vscode): preserve multi-question answers#1918
Draft
hogeheer499-commits wants to merge 1 commit into
Draft
Conversation
|
hogeheer499-commits
force-pushed
the
agent/fix-vscode-multi-question-1880
branch
from
July 19, 2026 11:38
90a7ce2 to
e81d586
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related Issue
Resolves #1880
The VS Code dialog submitted the answer to
questions[0]immediately, so any remaining questions in the sameAskUserQuestionrequest were dropped.The dialog now walks through the questions in order and submits once, after the last answer. Selection and custom-input state are reset between questions, and multi-question prompts show the current position.
I added a jsdom regression test covering two questions and verified that nothing is submitted after the first answer. The full VS Code suite passes (289 tests), along with both typechecks and the production webview build. Oxlint reports no errors; its four shorthand-arrow warnings were already present.
There is no changeset because the VS Code extension is private rather than part of the published
@moonshot-ai/kimi-codepackage. This restores existing behavior, so no documentation change is needed.Checklist
gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.