The redesigned effort dialog described above is gated behind the tengu_grey_step2 feature flag, which defaults to { enabled: false }.
Feature-flagged (disabled by default, server-controlled rollout)
- The
tengu_grey_step2flag controls whether the dialog appears and provides its title and description text - A separate
tengu_quartz_falconflag also influences the default effort level for Opus 4.6 - First-party users who previously dismissed the old effort dialog won't see the new one until
tengu_grey_step2is enabled server-side - API users (
By()orwb6()) can also be enrolled via the same flag
Dialog visibility (search for "effortCalloutV2Dismissed") — zIq() at line ~588370 checks zb6().enabled
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_grey_step2 Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.68: 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.68. 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.