Updates can arrive as a compressed build, so downloads get smaller with no setting to change.
What's wrong with this entry?
The 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.
- 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
.zstvariant, 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. - 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. - Successful downloads now report a
compressedfield ontengu_binary_download_success. - Manifest fetches now retry when the connection drops.
Decompressed binary exceeds the manifest size of , Decompressed binary larger than manifest size
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.221
Four dead-code probes deleted along with the legacy paths they measured
Both mention updater