{"version":"2.1.281","anchor":"sse-transport-can-hold-incoming-frames-and-closes-through-em","canonical_anchor":"sse-transport-can-hold-incoming-frames-and-closes-through-em","heading":"SSE transport can hold incoming frames and closes through emitClose","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/sse-transport-can-hold-incoming-frames-and-closes-through-em","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### SSE transport can hold incoming frames and closes through emitClose\n\nThe SSE connection can now hold incoming messages in a queue instead of handling them straight away, and closes through one shared step\n\n**Unclear.** The finding does not say what puts the connection into held mode or when the queued messages are handled.\n\n**What**\n\nSSE is a kind of connection in which a server keeps sending messages to Claude Code. The part that handles it, `SSETransport`, has a new held mode. While it is held, incoming messages are saved in a queue, together with a policy reading and the time each one arrived, instead of being handled at once. Closing the connection now always goes through a single `emitClose` step.\n\n**Why**\n\nThis is an internal change to how Claude Code receives streamed messages. Nothing you do or see changes because of it."}