{"version":"2.1.281","anchor":"artifact-publish-bodies-can-be-gzipped-with-a-deadline-rati","canonical_anchor":"artifact-publish-bodies-can-be-gzipped-with-a-deadline-rati","heading":"Artifact publish bodies can be gzipped, with a deadline-ratio check","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/artifact-publish-bodies-can-be-gzipped-with-a-deadline-rati","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Artifact publish bodies can be gzipped, with a deadline-ratio check\n\nLarge Artifact frame publishes are now gzip-compressed, falling back to plain uploads when compression would be too slow or is refused\n\n**What**\n\nWhen Claude Code publishes an Artifact frame (`frame_publish`), it now compresses large bodies with gzip, a standard way of shrinking data before sending it. How it decides:\n\n- It first tests a sample to see how well the data compresses.\n\n- It sends the body uncompressed if gzip could not finish \"inside the server's 60-second read limit\".\n\n- If the server rejects the compressed body, it resends it uncompressed and may stop using gzip from then on.\n\nThe usage data it reports gains `artifact_publish_gzip_request_body`, and a `bad_json` reason is recorded when the body is not valid data.\n\n**Why**\n\nLarge publishes send less data. The fallbacks mean a publish still goes through when compression would be too slow or the server does not accept it.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}