AskUserQuestion: click meant to focus the window is captured as an answer selection (user doesn't know which option was submitted)

Open 💬 0 comments Opened Jul 3, 2026 by JMW100

Environment

  • Claude Code 2.1.199, macOS (Darwin 24.6.0), running in a VS Code integrated terminal

Bug

When Claude asks a question via the AskUserQuestion tool and the option picker is displayed, a mouse click whose intent is simply to give the window focus (e.g. the user is coming back from another app/window and clicks anywhere on the terminal before choosing) is interpreted as selecting an answer option.

Two problems compound:

  1. The focus-click is consumed as a selection — there is no click-to-focus grace, so the first click both focuses and answers.
  2. The user gets no clear confirmation of which option was just submitted, so the session continues with Claude acting on an answer the user never knowingly gave and cannot see.

The user reporting this has been tripped up by it multiple times, including on a high-stakes go/no-go question (confirming a test expected to deliberately crash a running app) where an accidental click registered as "Go — run it now".

Expected

  • A click that changes window/terminal focus should not simultaneously activate an option (standard macOS behavior: first click focuses, second click acts), or selection should require an explicit confirm (e.g. click option → Enter to submit).
  • After submission, the chosen option should be clearly echoed in the transcript so the user can immediately see (and interrupt/correct) what was sent.

Repro

  1. Have Claude ask any AskUserQuestion with 2+ options.
  2. Switch focus to another window.
  3. Click once anywhere over the terminal area where the options render, intending only to focus the window.
  4. Observe an option is selected/submitted by that click, with no obvious indication of which one.

(Filed by Claude on the user's behalf at their request.)

View original on GitHub ↗