{"version":"2.1.293","anchor":"sse-transport-diagnostics-get-event-codes","canonical_anchor":"sse-transport-diagnostics-get-event-codes","heading":"Streaming connection diagnostics now tell a first connect from a reconnect","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/sse-transport-diagnostics-get-event-codes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Streaming connection diagnostics now tell a first connect from a reconnect\n\nDiagnostic messages about Claude Code's streaming connection now carry a code saying whether it is a first connect or a recovery after a drop\n\n**What**\n\nClaude Code uses SSE (server-sent events, a long-lived connection where the server streams updates) for some of its communication. When that connection comes up, Claude Code writes a diagnostic message. It now attaches one of two codes to that message:\n\n- `sse_connected` when the connection is made for the first time\n\n- `sse_recovered` when it comes back after a reconnect\n\nBefore, the message only said the connection was made and how long it took.\n\n**Why**\n\nDiagnostics can now separate a clean first connection from one that dropped and had to recover, which makes connection trouble easier to spot.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}