{"version":"2.1.242","anchor":"binary-updates-can-download-a-zstd-compressed-build","canonical_anchor":"binary-updates-can-download-a-zstd-compressed-build","heading":"Binary updates can download a zstd-compressed build","tier":"notice","area":"Updater","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/binary-updates-can-download-a-zstd-compressed-build","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Binary updates can download a zstd-compressed build\n\nUpdates can arrive as a compressed build, so downloads get smaller with no setting to change.\n\n**What**\n\nThe updater can now fetch a compressed build and decompress it locally, cutting download size. There is no client setting: it happens when the release channel's update manifest publishes a checksum and size for your platform, so it can be enabled per platform without shipping a new Claude Code.\n\n**Details**\n\n- The updater fetches a compressed manifest alongside the normal one. When it supplies a 64-character hex checksum for your platform and a positive size, it downloads the `.zst` variant, streams it through a zstd decoder, enforces the manifest's decompressed size as a hard cap mid-stream, and verifies the sha256 of the compressed bytes.\n- Any failure (missing fields, checksum mismatch, size overrun, a rejected zstd frame) falls back silently to the uncompressed URL and records `update_download_zst_fallback`.\n- Successful downloads now report a `compressed` field on `tengu_binary_download_success`.\n- Manifest fetches now retry when the connection drops.\n\n**Evidence**\n\n`Decompressed binary exceeds the manifest size of `, `Decompressed binary larger than manifest size`\n\n- Area: Updater\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}