tengu_atomic_ocean

A Claude Code feature flag, read out of the shipped bundle. It was in the build from v2.1.236 and was gone by v2.1.288.

Releases whose published page names tengu_atomic_ocean.

1. v2.1.300 14 Oct 2026
   A remote switch next to request compression has been removed

   A remotely controlled switch that sat beside the request compression setting is no longer read by Claude Code

   gate cited by this entry, found in this entry's text

2. v2.1.282 24 Sep 2026
   Compression level for gzipped requests can now be set

   CLAUDE_CODE_GZIP_REQUEST_BODY_LEVEL sets a gzip level from 1 to 9 for requests Claude Code already compresses

   gate cited by this entry

3. v2.1.236 19 Aug 2026
   The 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, found in this entry's text

4. v2.1.236 19 Aug 2026
   Gzipped 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, found in this entry's text

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.

One row per unbroken stretch of one reading, newest first, from snapshots taken every twenty-five minutes or so. No longer carried is not off: it means the flag server stopped returning the gate at all, which is what a retired experiment looks like. The version column is what was installed when the reading was taken, not what caused it.

The earliest release whose published evidence quoted tengu_atomic_ocean was v2.1.236, 19 Aug 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.

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.