AskUserQuestion auto-selects default answer after ~60s idle — no way to configure or disable (v2.1.198)

What happened

On Claude Code v2.1.198, when Claude uses the AskUserQuestion tool to ask a multiple-choice question, the prompt auto-selects the default/first option after ~60 seconds of no user input, then continues the turn as if I had answered.

This means a choice I never made gets silently committed. There is no documented way to lengthen this idle window or disable the auto-answer so the question waits until I actually respond.

Expected behavior

A supported setting to control this — e.g. a settings.json key or env var to:

• set the idle window (e.g. askUserQuestion.idleTimeoutMs), and/or
• disable the auto-answer entirely so the prompt blocks until answered.

Environment

• Claude Code: 2.1.198
• OS: Windows 11 Enterprise (26200)
• Terminal: interactive CLI session

Notes / prior art

• The behavior is undocumented — I checked the changelog for 2.1.185–2.1.198 and found no entry describing an AskUserQuestion idle timeout or auto-select.
• The only public 60s idle mechanism I could find is the idle_prompt Notification hook, whose timeout is hardcoded (#13922). A Notification hook on idle_prompt can alert the user but cannot extend or suppress the timer (Notification is display-only).
• Related: #30740 (request for configurable AskUserQuestion timeout, closed as not planned), #70294 (interactive prompts hang / not surfaced to remote channels).

Request

Please either document the current 60s auto-default behavior, or add a config knob to adjust/disable it. Reopening #30740 may be the right home for this since the behavior now ships live rather than being hypothetical.