Claude Code v2.1.311 · 26 Oct 2026
Remote session updates recover from expired logins and refuse third-party providers
Updating a bridge session now retries after a login failure and is refused for third-party providers; move-to-cloud also retries once with a fresh token
You'll notice Tier: how much it should matter to you
2 Useful: my rating, 1 to 5
2 Signal: worth watching, 1 to 5
Sessions Area: what it touches
Improvements Kind: in v2.1.311, 26 Oct 26
Improvements Section of the release
What
A bridge session links your local Claude Code to a remote session. Updating one has changed:
If you use a third-party provider, meaning Claude through a company other than Anthropic, the update is now refused.
The login token comes from a separate source for remote sessions instead of only your Claude.ai login.
If the server says the login is not valid, Claude Code now tries to recover the login in the background instead of just failing.
Moving a session to the cloud also retries once with a refreshed token when the login is rejected.
Why
Remote and cloud sessions should hit fewer login failures after a token expires.
See this entry in the whole of v2.1.311 →
← Previous · 107 of 425
Restarted background sessions no longer always resume the interrupted turn
You'll notice Background Agents
In v2.1.311 Improvements release-page order
Next → · 109 of 425
MCP servers can be told a session's own directory as their root
You'll notice MCP