By 4:22pm today, Claude Code Desktop had accumulated 5h46 of waiting across 6 overlapping sessions: 23 stalls of ~15 minutes each.
I honestly don't understand how this is still possible.
@bcherny@AnthropicAI@ClaudeDevs@claudeai
https://t.co/S0M1YWfRUA
@amdad121@claudeai If “Waiting for Claude…” sits there for minutes, it may not be Claude thinking. I measured 7 silent stalls this morning alone, including two at 15 minutes.
I documented the pattern, logs and GitHub issue here:
https://t.co/MdHjCkWNbQ
The GitHub issue about Claude Code silently freezing got delayed today… because Claude Code froze while working on it. Twice. 4 minutes to load a tool schema.
Numbers in thread.
@ric_guia@petergyang If “Waiting for Claude…” sits there for minutes, it may not be Claude thinking. I measured 7 silent stalls this morning alone, including two at 15 minutes.
I documented the pattern, logs and GitHub issue here:
https://t.co/MdHjCkWNbQ
The GitHub issue about Claude Code silently freezing got delayed today… because Claude Code froze while working on it. Twice. 4 minutes to load a tool schema.
Numbers in thread.
@bwjbuild If “Waiting for Claude…” sits there for minutes, it may not be Claude thinking. I measured 7 silent stalls this morning alone, including two at 15 minutes.
I documented the pattern, logs and GitHub issue here:
https://t.co/MdHjCkWNbQ
The GitHub issue about Claude Code silently freezing got delayed today… because Claude Code froze while working on it. Twice. 4 minutes to load a tool schema.
Numbers in thread.
Claude Code stuck on “Waiting for Claude…”?
7 silent stalls this morning. +20 in five days. ~4 hours lost. One 51-minute hang.
Today it waited 30 minutes after “read this Markdown file.”
This isn’t Claude thinking. It’s a known client bug:
https://t.co/wnoKWbywtS
@ClaudeDevs@claudeai
@namannn04 If the wait ever passes 15 silent minutes, it may not be thinking at all. I measured 15 dead-connection stalls in 5 days, one 51-min hang: https://t.co/MdHjCkWNbQ
The GitHub issue about Claude Code silently freezing got delayed today… because Claude Code froze while working on it. Twice. 4 minutes to load a tool schema.
Numbers in thread.
@me_for_real42 Known bug, and it's worse than 6 min: I measured 15 silent stalls in 5 days, one 51-min hang. Dead connections the client never detects — analysis here: https://t.co/MdHjCkWNbQ
The GitHub issue about Claude Code silently freezing got delayed today… because Claude Code froze while working on it. Twice. 4 minutes to load a tool schema.
Numbers in thread.
@alleneubank Same here, and I measured it: 15 silent stalls in 5 days from the session logs, one 51-min hang. It's dead connections the client never detects — full analysis: https://t.co/MdHjCkWNbQ
The GitHub issue about Claude Code silently freezing got delayed today… because Claude Code froze while working on it. Twice. 4 minutes to load a tool schema.
Numbers in thread.
@AIShortcuton Yes — measured it from session logs: 15 stalls in 5 days, ~4h of dead wall time, one 51-min hang. Root cause documented (dead connections, no watchdog): https://t.co/MdHjCkWNbQ
The GitHub issue about Claude Code silently freezing got delayed today… because Claude Code froze while working on it. Twice. 4 minutes to load a tool schema.
Numbers in thread.
Hours of work silently lost to a client that can't detect a dead connection — ~4h in 5 days, one user. No maintainer response; support promised an email that never came. @AnthropicAI@claudeai@ClaudeDevs the telemetry to size this already exists: CLAUDE_SLOW_FIRST_BYTE_MS.
The GitHub issue about Claude Code silently freezing got delayed today… because Claude Code froze while working on it. Twice. 4 minutes to load a tool schema.
Numbers in thread.
Not just me: the same 5-20 min silent hangs have been reported since February. Issue 26224 alone has 150 thumbs-up and 128 comments, still open. There are entire third-party guides teaching people to "send a message to wake it up". That's a workaround culture, not a niche bug.