tengu_gzip_request_body_latch_cleared
A Claude Code feature flag, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.
What it is
The gzip decision now records exactly why it skipped, though compression stays off without a server value.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.236.
Presence across releases
The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.
Gate readings
No release here has a gate table behind it for this flag. Most published releases have none at all: the readings exist only for versions the pipeline captured flag state on.
Changelog entries naming it
-
v2.1.236The compression decision is rebuilt from a one-liner into a full decision path
The gzip decision now records exactly why it skipped, though compression stays off without a server value.
gate cited by this entry
-
v2.1.236Gzipped API request bodies, gated off, with a retry-and-latch kill switch
Requests to the API can be gzip compressed, but both switches default off so nothing compresses.
gate cited by this entry
Documentation pages
None of Anthropic's documentation pages this site has a copy of carries this name.
Names beside it
Every feature flag in the inventory starting tengu_gzip_request_body, up to twelve of them.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.