{"version":"2.1.311","anchor":"bridge-session-patch-refuses-third-party-providers-and-recov","canonical_anchor":"bridge-session-patch-refuses-third-party-providers-and-recov","heading":"Remote session updates recover from expired logins and refuse third-party providers","tier":"notice","area":"Sessions","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/bridge-session-patch-refuses-third-party-providers-and-recov","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Remote session updates recover from expired logins and refuse third-party providers\n\nUpdating 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\n\n**What**\n\nA bridge session links your local Claude Code to a remote session. Updating one has changed:\n\n- If you use a third-party provider, meaning Claude through a company other than Anthropic, the update is now refused.\n\n- The login token comes from a separate source for remote sessions instead of only your Claude.ai login.\n\n- If the server says the login is not valid, Claude Code now tries to recover the login in the background instead of just failing.\n\nMoving a session to the cloud also retries once with a refreshed token when the login is rejected.\n\n**Why**\n\nRemote and cloud sessions should hit fewer login failures after a token expires.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: yes"}