{"version":"2.1.68","anchor":"server-controlled-effort-dialog-gradual-rollout","canonical_anchor":"server-controlled-effort-dialog-gradual-rollout","heading":"Server-controlled effort dialog [Gradual Rollout]","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.68\/e\/server-controlled-effort-dialog-gradual-rollout","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.68","markdown":"### Server-controlled effort dialog [Gradual Rollout]\n\n**What**\n\nThe redesigned effort dialog described above is gated behind the `tengu_grey_step2` feature flag, which defaults to `{ enabled: false }`.\n\n**Status**\n\nFeature-flagged (disabled by default, server-controlled rollout)\n\n**Details**\n\n- The `tengu_grey_step2` flag controls whether the dialog appears and provides its title and description text\n- A separate `tengu_quartz_falcon` flag also influences the default effort level for Opus 4.6\n- First-party users who previously dismissed the old effort dialog won't see the new one until `tengu_grey_step2` is enabled server-side\n- API users (`By()` or `wb6()`) can also be enrolled via the same flag\n\n**Evidence**\n\nDialog visibility (search for `\"effortCalloutV2Dismissed\"`) \u2014 `zIq()` at line ~588370 checks `zb6().enabled`\n\n- Flag `tengu_grey_step2`: Not enough to say (read for one account on one subscription tier against v2.1.68; this account: no value returned, anonymous baseline: no value returned, compiled default: 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."}