{"version":"2.1.312","anchor":"worker-socket-may-offer-compression-when-dialing","canonical_anchor":"worker-socket-may-offer-compression-when-dialing","heading":"Cloud worker connections can ask for compression","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/worker-socket-may-offer-compression-when-dialing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Cloud worker connections can ask for compression\n\nClaude Code's worker connection can now offer compression when it connects, and a fault in how the connection was stored is fixed\n\n**What**\n\nWhen Claude Code runs as a worker, for example in a cloud session, it opens a lasting two-way connection called a WebSocket. When opening it, Claude Code now decides whether to offer compression, which shrinks the data sent. If it does, it says so in the connection address. If that decision fails, Claude Code logs an error and connects without offering compression.\n\nA fault is also fixed: the opened connection used to be stored in the wrong place, and it is now stored where it belongs.\n\n**Why**\n\nCompression can cut the amount of data a cloud worker session sends and receives.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}