Claude Code 2.1.181: Major Startup Reliability Improvements
Claude CodeClaude Code 2.1.181 ships a concentrated set of startup reliability improvements. It resolves a 15 second blank terminal on slow networks, a 120ms per launch regression from 2.1.169, a startup crash caused by corrupted .claude.json entries, and a macOS interface freeze when Spotlight is reindexing. Together they make Claude Code much more dependable to open in real world conditions.
Sources & Mentions
3 external resources covering this update
Startup is now much more reliable
Claude Code 2.1.181 resolves four distinct startup failure modes that have been frustrating users in real-world conditions. Each targets a different root cause, but they share a pattern: Claude Code was blocking on external dependencies, network fetches, disk activity, or corrupted state, in ways that froze the UI, crashed on launch, or added latency before the first prompt.
The 15 second blank terminal
The most visible fix addresses a case where startup blocks with a blank terminal for up to 15 seconds when the account settings fetch is slow on a degraded network. This hit users on VPNs, corporate proxies, and intermittent connections, exactly where a dependable tool matters most. Claude Code no longer waits on that fetch before rendering the UI.
A 120ms per launch regression
A regression introduced in 2.1.169 added roughly 120ms of latency to every launch in fresh environments, because the first prompt was waiting for a managed-settings fetch even when no MCP servers were configured. The fix removes that wait for the common case, restoring snappy startup for the majority of users.
Crash on a corrupted .claude.json
Claude Code was crashing on launch with a TypeError: Cannot read properties of null when .claude.json contained corrupted null project entries. The fix adds defensive handling for null entries, so Claude Code starts normally even when the project config file is partially malformed.
macOS freeze during Spotlight reindexing
On macOS, the fullscreen interface could freeze at session start, with Ctrl+C unresponsive, when Spotlight was actively reindexing files in the background. The cause was invisible to the user. The fix prevents Spotlight disk activity from blocking session initialization.
Why they matter together
Individually these are edge cases. Together they improve the reliability of the most critical moment in the tool, opening it. A blank terminal, a crash, or a frozen interface all undermine trust in Claude Code as a daily driver, no matter how well everything else works once a session is running.