{"version":"2.1.295","anchor":"remote-session-init-message-ignored-sse-401-refresh-hardene","canonical_anchor":"remote-session-init-message-ignored-sse-401-refresh-hardene","heading":"Remote sessions no longer show a start-up message and handle login refresh failures","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/remote-session-init-message-ignored-sse-401-refresh-hardene","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Remote sessions no longer show a start-up message and handle login refresh failures\n\nRemote session views now skip the start-up system message, and a failed login refresh after a rejection is handled cleanly\n\n**What**\n\nWhen you view a session that is running remotely, Claude Code has changed how it handles messages and connection problems:\n\n- The system start-up message is now ignored instead of being shown as a message.\n\n- When the server rejects your login (an HTTP 401 error) and refreshing the login fails, that failure is now treated as a plain \"no\" instead of an error.\n\n- When reconnect attempts run out, the connection now records the cause as `exhausted`.\n\n**Why**\n\nThis removes a duplicate start-up line from remote session views. A failed login refresh no longer breaks the connection handling.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}