Skip to content

Conversation

@ThomasK33
Copy link
Member

Fix two issues with the ask_user_question tool UI:

  1. Softer indicator color - The "Mux has a few questions" status indicator was using a bright yellow that was harsh on the eyes. Changed to plan-mode blue which is softer and semantically indicates "awaiting user input".

  2. Enter key advances - When selecting "Other" and typing a free-text answer, pressing Enter now advances to the next question (when text is non-empty).


📋 Implementation Plan

Plan: Fix ask_user_question UI Issues

Summary

Fix two issues:

  1. Replace eye-burning bright yellow "Mux has a few questions" indicator with a softer color
  2. Add Enter key handling to advance from "Other" text input

Estimated net LoC: +8


Issue 1: Overly Bright Yellow Status Indicator

Problem: The "Mux has a few questions" indicator in WorkspaceStatusIndicator.tsx uses hardcoded bg-yellow-500/20 text-yellow-400 which is too bright/harsh.

Solution: Use the app's plan-mode blue (bg-plan-mode-alpha text-plan-mode-light) for consistency with "waiting for input" semantics.


Issue 2: Enter Key Doesn't Advance from Other Input

Problem: When the user selects "Other" and types a free-text answer, pressing Enter does nothing.

Solution: Add onKeyDown handler to the Input that advances to the next question when Enter is pressed and text is non-empty.


Generated with mux • Model: anthropic:claude-opus-4-5 • Thinking: high

- Replace bright yellow with plan-mode blue for 'Mux has a few questions'
- Add Enter key handler to Other text input to advance to next question

Change-Id: I39040995ad67af17ca248b1741bf193be7baa541
Signed-off-by: Thomas Kosiewski <tk@coder.com>
@ThomasK33 ThomasK33 added this pull request to the merge queue Dec 16, 2025
onKeyDown={(e) => {
if (e.key === "Enter" && currentDraft.otherText.trim().length > 0) {
e.preventDefault();
setActiveIndex(activeIndex + 1);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks fishy for outofbound

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it’s fine. You can’t enter anything on the summary page, so you wouldn’t be able to press Enter there and go out of bounds.

Merged via the queue into main with commit f50e2db Dec 16, 2025
20 checks passed
@ThomasK33 ThomasK33 deleted the question-ui-q060 branch December 16, 2025 18:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants