🤖 feat: improve ask_user_question UX with auto-advance and descriptions #1176
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
Improve the
ask_user_questiontool UX with three enhancements:Changes
useEffectto auto-advance when single-select option is chosen (skips "Other" since text input is needed)hasUserInteractedref to prevent auto-advance on initial rendergetDescriptionForAnswerhelper to look up descriptions📋 Implementation Plan
Plan: Improve
ask_user_questionUXSummary
Enhance the multi-choice questionnaire UI with:
Current Behavior
Proposed Changes
File:
src/browser/components/tools/AskUserQuestionToolCall.tsx1. Auto-advance for single-select questions (~+15 LoC)
When a user selects an option for a non-multiSelect question:
Implementation:
useEffectthat watchesdraftAnswerschangesactiveIndex2. Selection type indicator (~+10 LoC)
Add a small text hint below the question text:
This makes it immediately clear to the user what kind of input is expected.
3. Show descriptions in answer displays (~+30 LoC)
A. In the summary view (during execution):
Currently shows:
✓ Header: LabelProposed: Show the description in a smaller muted text below when hovering or always inline.
B. In the completed view (after submission):
Currently shows:
• Question: AnswerProposed: Add the description for the selected option(s) in a muted text line below.
Implementation:
Estimated LoC Change
Alternative Considered
Use radio buttons for single-select vs checkboxes for multi-select
This would visually distinguish the two modes, but:
Decision: Keep checkboxes but add text indicator for clarity.
Generated with
mux• Model:anthropic:claude-opus-4-5• Thinking:high