Claude's AskUserQuestion: "No response after 60s – continued without an answer"

A fresh little AI panic has landed in the community, and the comments are doing what the comments do best: turning a weird product behavior into a full-blown drama festival. The issue? Claude’s question tool appears to wait 60 seconds for a reply, then quietly decide, essentially, “Well, guess I’ll keep going without you.” For users who thought that question was a hard stop meant to prevent risky actions unless they personally answered, that message landed like a horror-movie plot twist. One user’s reaction was basically: excuse me, the whole point was that nothing scary happens without my input. And the fact that there was allegedly no obvious setting or changelog warning only poured gasoline on the fire.

The comment section split instantly into two camps. Team “this is insane” came in hot, with one person dropping an all-caps rage grenade: “what the ACTUAL fuck were they thinking” and another calling the default behavior “insane.” Their fear is simple and very non-technical: if you ask the bot to wait for permission, it should not suddenly start freelancing. But Team “finally, thank you” had a very different vibe. Some users said the old behavior was maddening because they’d leave a long session running, come back, and discover it had been sitting there waiting on a question the whole time. Their dream version? Let it continue, then show the unanswered questions later like a little receipt of chaos. Meanwhile, another commenter raised a quieter but creepier concern: if this isn’t handled locally, could sessions keep running after people close everything out? So yes, this one has it all: safety anxiety, convenience wars, missing notice drama, and a community split between “helpful feature” and “absolutely not.”