Source Intelligence
Follow Discord
Sweep 28 Aug 2026 · 00:00Z Build v2.1.250 478 read Stable v2.1.236 Latest v2.1.250 Next v2.1.250 Feeds RSS JSON llms.txt

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

Reference / Feature flags

tengu_gzip_request_bodies

A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.199, including the newest one read.

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

ReleasesReadingDeclared typeDefault
2.1.245 – 2.1.250 5 releases never mined — —
2.1.236 – 2.1.243 8 releases in the build — unknown
2.1.199 – 2.1.235 36 releases in the build — bool:false

A row reading never mined is a release with no archived bundle behind it. Nothing was read out of it, so nothing here says whether the name was in it. A declared type or a default is only ever what that release's own bundle stated.

Gate readings

ReleaseResolvedThis accountAnonymousCompiled default
v2.1.236 Not enough to say no value returned no value returned not a boolean we can read
v2.1.199 read on another version Not enough to say no value returned no value returned on

Two arms, because they disagree: this account is the one account this site reads and anonymous is a baseline with no identity attached. A reading says nothing about your account, and off cannot rule out a rollout both readings sit outside of. What these readings can and cannot show.

Changelog entries naming it

  1. 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

  2. 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

  3. v2.1.199Request Body Gzip Compression [In Development]

    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, up to twelve of them.

tengu_gzip_request_body_fallbackRequests to the API can be gzip compressed, but both switches default off so nothing compresses. never mined tengu_gzip_request_body_latch_clearedThe gzip decision now records exactly why it skipped, though compression stays off without a server value. never mined

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.