{"version":"2.1.247","anchor":"gzipped-request-bodies-for-remote-control-traffic-off-by-def","canonical_anchor":"gzipped-request-bodies-for-remote-control-traffic-off-by-def","heading":"Gzipped request bodies for Remote Control traffic, off by default","tier":"soon","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/gzipped-request-bodies-for-remote-control-traffic-off-by-def","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Gzipped request bodies for Remote Control traffic, off by default\n\nRemote Control requests can be gzip-compressed, but it is switched off in this build.\n\n**What**\n\nRequests to the Remote Control worker can now be sent with gzip-compressed bodies. It is decided by the flag `tengu_gentle_hammock`, which is compiled in as off, and can be forced either way with `CLAUDE_CODE_GZIP_CCR_REQUEST_BODIES`. It only applies on the Bun runtime, and only for string bodies of at least 1024 characters.\n\n**Details**\n\n- Refusal reasons are recorded as `env_off`, `not_bun_runtime`, `below_min_size` and `flag_off`.\n- Proxies, mTLS, unix sockets and custom CA certificates all disable it.\n- The flag name does not exist in the previous release, so nothing turns this on unless the account's remote config serves it.\n\n**Usage**\n\n`CLAUDE_CODE_GZIP_CCR_REQUEST_BODIES=1 claude` **Evidence** `CLAUDE_CODE_GZIP_CCR_REQUEST_BODIES`, `gzipRequestBodyFetch`\n\n- Area: Remote Control\n- Names: `CLAUDE_CODE_GZIP_CCR_REQUEST_BODIES`, `tengu_gentle_hammock`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}