Claude Code Background Agent Sessions Now Auto-Update Without Cold Restart
Claude CodeClaude Code 2.1.163 eliminates a frustrating delay that affected developers relying on background agent sessions: when Claude Code auto-updated to a new version, opening a background session after the update previously triggered a cold restart that could take several seconds. Background sessions now update silently in the background, so resuming a session after an auto-update is immediate. This change is particularly valuable for teams running multiple parallel background agents or long-running autonomous tasks across update cycles.
Featured Video
A video we selected to help illustrate this changelog
Sources & Mentions
4 external resources covering this update
Background Agent Sessions Now Update Silently
One of the rougher edges of Claude Code's background agent system has been smoothed over in version 2.1.163: background sessions no longer wait on a cold restart when Claude Code installs a new version of itself.
The Problem This Solves
Claude Code ships frequent updates, often multiple releases per day. Until now, if a background session was open when an update arrived, the first time a developer returned to that session after the update they would be greeted with a multi-second cold restart delay while the new binary initialized. For teams running concurrent agents across complex tasks (Claude Code's claude agents interface supports managing many sessions simultaneously) this friction compounded quickly.
What Changed
Anthropic updated the background daemon architecture so that version upgrades happen silently while sessions are idle. The session state persists on disk under ~/.claude/ through the transition. When a developer opens a session after an update, it attaches immediately to the already-running (or already-updated) daemon rather than waiting for a fresh initialization cycle.
This improvement builds on a series of background agent reliability fixes in recent releases, including work in v2.1.162 that improved background service startup to wait out endpoint-security scanning of new binaries (which had been causing 5-second failures on machines with aggressive EDR software), and fixes in v2.1.160 that addressed multiple session loss bugs when reconnecting after overnight idle.
Why It Matters for Agentic Workflows
As Claude Code's claude agents view becomes the default way many developers manage parallel work, the quality of the session lifecycle (launch, background, update, resume) directly affects how much autonomous work can be trusted to run without supervision. Eliminating cold-restart delays after updates removes one more reason for a developer to hesitate before handing off a long-running task to a background agent.