Source Intelligence
Follow Discord

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.

← All of v2.1.68 Home All releases ←olderv2.1.67 v2.1.69newer→
Claude Code v2.1.68

Server-controlled effort dialog [Gradual Rollout]

Feature flag
tengu_grey_step2 Not enough to say

Nothing 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

What

The redesigned effort dialog described above is gated behind the tengu_grey_step2 feature flag, which defaults to { enabled: false }.

Status

Feature-flagged (disabled by default, server-controlled rollout)

Details
  • The tengu_grey_step2 flag controls whether the dialog appears and provides its title and description text
  • A separate tengu_quartz_falcon flag 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_step2 is enabled server-side
  • API users (By() or wb6()) can also be enrolled via the same flag
Evidence

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.

See this entry in the whole of v2.1.68 →