{"version":"2.1.312","anchor":"workersocket-close-telemetry-adds-compression-fields-and-rep","canonical_anchor":"workersocket-close-telemetry-adds-compression-fields-and-rep","heading":"Remote worker connection reports now record whether compression was used","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/workersocket-close-telemetry-adds-compression-fields-and-rep","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Remote worker connection reports now record whether compression was used\n\nUsage reports about the remote worker connection closing now note whether compression was offered and used, and sort closes differently\n\n**What**\n\nWhen the connection between Claude Code and a remote worker closes, Claude Code sends a usage report about it. That report now includes:\n\n- `offered_compression`, whether compression was offered\n\n- `compressed`, whether the connection was compressed\n\nThe rule that decides which closes count as normal and which count as errors also changed. It used to be a fixed list of reasons (aborted, renewed, shutdown and one specific close code).\n\n**Why**\n\nThis suggests compression is being added to the remote worker connection.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}