{"version":"2.1.312","anchor":"remote-sse-reconnect-handles-a-401-on-a-dial-that-carried-no","canonical_anchor":"remote-sse-reconnect-handles-a-401-on-a-dial-that-carried-no","heading":"Remote sessions recover from a sign-in error on a connection that had no token","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/remote-sse-reconnect-handles-a-401-on-a-dial-that-carried-no","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Remote sessions recover from a sign-in error on a connection that had no token\n\nIf a remote session's live connection is refused because it carried no sign-in token, Claude Code now waits for one and reconnects\n\n**What**\n\nRemote sessions keep a live connection open so the server can stream updates to Claude Code. This kind of connection is called SSE (server-sent events). If the server refuses that connection with a 401 error (\"not signed in\") and the connection was made without any sign-in token, Claude Code now waits for the part of itself that holds the token to supply one, then connects again. It logs \"401 on SSE connect that carried no credential\" when this happens.\n\nBefore, Claude Code only tried its usual token refresh in this situation.\n\n**Why**\n\nThis should make remote sessions more reliable when a connection starts before a sign-in token is ready.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}