Claude Code 2.1.185 raises stream-stall retry wait to 20s

• ClaudeCodeLog's release post says Claude Code 2.1.185 shipped with one user-visible CLI change: the stream-stall hint now waits 20 seconds before surfacing a retry notice.
• According to the changelog snippet, the message text changed from "No response from API · Retrying in …" to "Waiting for API response · will retry in …", which reframes the pause as backend silence rather than a failed request.
• ClaudeCodeLog's metadata post says the release left prompt files, prompt tokens, and prompt-token mix unchanged, so this was not a prompt or tool-surface update.
• In a separate reply, Stephen Haney's rollout note said Anthropic had shipped a "big fix" the day before and was rolling it out slowly across users.

You can open the linked changelog source from the release thread, skim the metadata dump and prompt stats, and the oddest detail is how little else moved: ClaudeCodeLog's diff post reports a 0.1 kB bundle shrink with zero prompt-token changes. Stephen Haney's reply also suggests the retry tweak landed alongside a broader staged fix for a user-reported issue.

The only documented CLI change in 2.1.185 is the stall notice. The timer moved from 10 seconds to 20 seconds, and the copy now says "Waiting for API response" before the retry countdown appears.

That makes the release read like a small UX correction for slow upstream responses, not a behavior change to prompts, permissions, or tools.

ClaudeCodeLog's follow-up lists no prompt-file additions, no prompt-token changes, and an identical token mix across tools, system reminders, system data, skills, system prompts, and agent prompts. The bundle size also moved by just 0.1 kB.

For a version that was teased the same day as "about to be released", that is about as surgical as Claude Code updates get.

Stephen Haney's reply says Anthropic had already shipped a "big fix" the previous day and was rolling it out slowly to make sure it held up across users. The post does not name 2.1.185 directly, but it adds useful context for why a tiny retry-window tweak might have arrived inside a staged rollout instead of a broader visible release note.