{"version":"2.1.312","anchor":"worker-websocket-compression-fallback","canonical_anchor":"worker-websocket-compression-fallback","heading":"Remote sessions turn off connection compression when it causes trouble","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/worker-websocket-compression-fallback","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Remote sessions turn off connection compression when it causes trouble\n\nThe connection to a remote worker now switches off compression after failures that suggest compression is breaking it\n\n**What**\n\nThe live connection Claude Code keeps to a remote worker (a machine running a session elsewhere) now tracks whether data compression was offered on it. Compression is switched off after any of these:\n\n- The connection closes with code 1009, meaning a message was too big.\n\n- The connection ends several times in a row without being accepted.\n\n- A compressed connection never served anything.\n\nA new way for a connection to end, `deflate_keeps_context`, is also handled.\n\n**Why**\n\nSome network proxies break compressed connections. Falling back to an uncompressed connection makes remote sessions more reliable behind them.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}