fix(vscode): improve custom question answers - #11051
Merged
Merged
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (10 files)
Reviewed by claude-4.6-sonnet-20260217 · 562,351 tokens Review guidance: REVIEW.md from base branch |
lambertjosh
force-pushed
the
fix/question-custom-answer-selection
branch
from
June 10, 2026 12:48
4248062 to
69f193d
Compare
lambertjosh
force-pushed
the
fix/question-custom-answer-selection
branch
from
June 10, 2026 17:54
a975497 to
c175883
Compare
Contributor
Author
|
Validated the fixes for single-select questions. Left multi-select unchanged for now. working_question.mov |
kirillk
approved these changes
Jun 11, 2026
t7tran
pushed a commit
to t7tran/kilocode
that referenced
this pull request
Aug 14, 2026
…nswer-selection fix(vscode): improve custom question answers
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.
Summary
Single option question tool previously never actually showed the custom entry as selected, which was quite annoying and misleading. Additionally it would show two submit buttons which was unnecessary, since clicking the first one actually submitted the question. UX was poor.
Before
After
Details
Custom text entry previously left the radio selection visually out of sync and exposed two submit buttons. This keeps the selection and controls consistent without changing question reply lifecycle handling.