AskUserQuestion option chips intermittently fail to register a click

Status Closed — not planned
Maintainer reply None cached
Activity 2 comments · opened Jul 3, 2026 · closed Aug 26, 2026

Description

During a session, an AskUserQuestion card's option chip failed to register a click. The selection only went through after I typed a written fallback in plain text on the next turn. This has happened before across sessions, not a one-off.

Separately (same user, different sessions): mcp__visualize (show_widget) HTML/SVG widgets have occasionally shown vertical-scroll problems, content not fitting cleanly within the rendered widget area.

Impact

Breaks the fast card-driven decision flow. When a chip doesn't register, the model can't tell the difference between "user is still deciding" and "the click silently failed," so it either waits indefinitely or has to ask the user to confirm via text, which defeats the purpose of a structured choice UI.

Environment

Claude Code CLI, non-interactive/harness session.

What would help

  • Any known repro steps for the chip-selection misfire (specific option count, preview-field length/content, or timing)?
  • Guidance on widget content sizing (viewBox dimensions, HTML layout constraints) to avoid vertical-scroll in show_widget output.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗