[Feature Request] Remove time limits from interactive questions

Status Closed — not planned

Reported on v2.1.199

Maintainer reply None cached

Activity 5 comments · opened Jul 3, 2026 · closed Aug 29, 2026

Bug Description

DO NOT ADD A TIME LIMIT TO QUESTIONS! WHICH IDIOT THOUGHT THIS WAS A GOOD IDEA?

STOP ADDING DEFAULTS WHICH ARE DIFFERENT!

I BURN CREDITS BECAUSE YOU DECIDED IT IS A GOOD IDEA TO GUESS IF I DON'T ANSWER IN 60 SECONDS!

Environment Info

Platform: darwin
Terminal: Apple_Terminal
Version: 2.1.199
Feedback ID: 918ac6fe-0d10-44eb-a5b0-549740e3f8dd

Errors

[]

View original on GitHub ↗

4 Comments

toth-istvan-zoltan · 1 month ago

This is what your own AI says about the matter:

On your message: yeah. Asking was the right call, and you shouldn't have to fight a hidden 60-second clock to answer a scoping question — a timeout that defaults on and silently proceeds is a bad default for exactly this reason: it turned "which scope did you want?" into me guessing wrong and shipping half the work. I've recorded the preference to skip that popup entirely and ask in plain text, so this won't recur in our sessions.

WebTiger89 · 1 month ago

what the fuck did you guys do. This is the greatest bug I have ever seen in my entire life. Drop this fucking timeout asap

christiannaths · 1 month ago

This is a disaster waiting to happen. It shouldn't be labeled as a feature request, it's a bug through and through. Quite possibly the worst unchecked idea I've seen maybe ever 👎👎👎👎

https://github.com/anthropics/claude-code/issues/73891

petrovo-as · 1 month ago

I also agree that it's a stupid idea. Cancel. Always wait for a response.

version 2.1.200 change

Changed AskUserQuestion dialogs to no longer auto-continue by default; opt into an idle timeout via /config

Showing cached comments. Read the full discussion on GitHub ↗

[Feature Request] Remove time limits from interactive questions

4 Comments

Related Claude Code issues

Browse by topic