No way to disable auto-timeout / auto-select on AskUserQuestion prompts

Open 💬 0 comments Opened Jul 2, 2026 by Chuseok22

Description

When Claude Code presents a question to the user via AskUserQuestion (or similar confirmation prompts), if the user doesn't respond within some time window, the CLI appears to automatically proceed — either by selecting the "(Recommended)" option or by skipping/passing the question entirely.

This is disruptive in workflows where the user explicitly wants Claude to wait indefinitely for a decision (e.g. during brainstorming, plan approval, or any step where an unattended auto-choice could lead to unwanted actions).

Expected behavior

There should be a documented way (via settings.json or a CLI flag) to disable this auto-timeout/auto-select behavior for AskUserQuestion and require an explicit user response before continuing.

Actual behavior

  • No related setting key found in settings.json schema or official docs (checked permissions, model, and other documented categories).
  • No mention of this feature/behavior in recent changelog entries.
  • The timeout appears to be enforced at the client/harness layer, before the model has a chance to act on any instruction (e.g. CLAUDE.md rules telling it to wait) — so this can't be worked around via prompt-level instructions.

Request

  1. Document whether this timeout is intentional and configurable.
  2. If configurable, expose the setting key (e.g. permissions.questionTimeoutMs: 0 or similar) in settings.json.
  3. If not currently configurable, consider adding an option to disable it, since auto-selecting an option (even a "recommended" one) without explicit user consent can lead to unintended actions in agentic workflows.

View original on GitHub ↗