The Opus 1M context window default is controlled by the tengu_cobalt_compass feature flag with a default of false.
Feature-flagged, rolling out gradually.
- The function
UH()checkstengu_cobalt_compass— returnsfalseby default - Only applies to first-party users (not API key users or third-party)
- Excluded when
je()(demo mode) orZC()(certain restricted contexts) is active - Once enabled server-side, migration is automatic
Feature gate check (search for "tengu_cobalt_compass") — UH() at line ~532570
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_cobalt_compass On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.75: no gate table built for this version
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.75. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.