Single-select AskUserQuestion options need a radio control, matching the checkbox the multi-select variant already has

Status Open
Maintainer reply None cached
Activity 0 comments · opened Aug 4, 2026

Single-select AskUserQuestion options need a radio control, matching the checkbox the multi-select variant already has

Summary

The AskUserQuestion option list renders two variants — multiSelect: true and
multiSelect: false — with inconsistent selection affordances:

  • Multi-select: clicking a row surfaces a discrete checkbox control. Selection

state is unambiguous at a glance, even in a dense list.

  • Single-select: clicking a row applies only a subtle card treatment (thin

border + near-white tint). There is no discrete control. In the light theme the
selected row is very hard to distinguish from its unselected siblings.

The result: in a single-select dialog with 3–4 multi-line options, a user who has
selected the first row can barely tell that they have.

Ask

Give the single-select variant a radio button, using the same appear-on-click
state formatting the multi-select variant already uses for its checkbox. This is
a reuse of an existing, working pattern in the same component rather than new
design work — and it carries the conventional semantics (radio = one, checkbox =
many), so the control itself communicates the dialog's arity.

Why this framing rather than "increase the contrast"

Raising the tint or border weight on the selected card would help marginally, but
it leaves the two variants stylistically divergent and still relies on a
whole-row background difference — the weakest available signal in a list of
multi-line cards with their own internal text hierarchy. A discrete control is
both higher-contrast and self-labelling.

Environment

  • Claude Code desktop app (macOS), updaterLastSeenVersion 1.24012.11
  • App appearance mode: system, currently resolving to light
  • Most visible in the light theme; the light theme is where the selected-card

tint is closest to the unselected background

Note on configurability

There is no user-side workaround. ~/.claude/settings.json theme governs the
CLI only; ~/Library/Application Support/Claude/config.json exposes only
userThemeMode (light/dark/system). No accent, contrast, or per-element styling
setting exists for this component.

View original on GitHub ↗