The effort callout dialog for Opus 4.6 users has been redesigned with server-configurable content and a simplified option set.
- Dialog title and description are now fetched from the server (via
tengu_grey_step2feature flag) instead of being hardcoded - Options are simplified to three clear choices:
- "Use medium effort (recommended)"
- "Use high effort"
- "Use low effort" (new — previously only medium and high were offered)
- Removed verbose per-option descriptions and the "(current)" suffix labeling
- Uses a separate dismiss state (
effortCalloutV2Dismissed) so users who dismissed the old dialog may see the new one
Server-controlled effort dialog (search for "tengu_grey_step2") — zb6() at line ~162660, dialog at ohq() line ~588325
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.