{"version":"2.1.217","anchor":"four-new-unnamed-feature-flags-in-development","canonical_anchor":"four-new-unnamed-feature-flags-in-development","heading":"Four New Unnamed Feature Flags [In Development]","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.217\/e\/four-new-unnamed-feature-flags-in-development","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.217","markdown":"### Four New Unnamed Feature Flags [In Development]\n\nFour new feature flag constants have been added without any observable user-facing behavior yet:\n\n- `tengu_amber_astrolabe` (also: `CLAUDE_CODE_AMBER_ASTROLABE` env var)\n- `tengu_bison_cairn` (also: `CLAUDE_CODE_BISON_CAIRN` env var)\n- `tengu_larch_cistern` (also: `CLAUDE_CODE_LARCH_CISTERN` env var)\n- `tengu_alder_wicket` (also: `CLAUDE_CODE_ALDER_WICKET` env var)\n\nThese are infrastructure additions that will be wired to behavior in a future release.\n\n**Details**\n\n- `tengu_amber_astrolabe` \/ `CLAUDE_CODE_AMBER_ASTROLABE`: accessor `ekc()` is checked in `Fa_()` alongside the existing max\/autonomous mode gate (`VMe(e)`); when true, the autonomy system prompt section is injected even outside max mode, instructing Claude to proceed with reversible actions without asking \"Want me to\u2026?\" permission questions and to stop only for destructive actions or genuine scope changes\n- `tengu_bison_cairn` \/ `CLAUDE_CODE_BISON_CAIRN`: accessor `tkc()` gates the `\"delivering_work_max\"` system prompt slot (`el_`); when true, a `# Delivering work` instruction block is added telling Claude to: act on what is in the request rather than speculation; deliver complete work under stated assumptions; explicitly report blocked sub-tasks; carry mid-task questions to the end of a turn that also delivers progress (rather than blocking); and treat user reaffirmation as a final decision to proceed\n- `tengu_larch_cistern` \/ `CLAUDE_CODE_LARCH_CISTERN`: accessor `rkc()` gates the `\"overcorrection\"` system prompt slot (`tl_`); when true, a `# Corrections` instruction block is added telling Claude to: only correct errors that would change the user's code, conclusions, or decisions; state corrections plainly and continue without apology, preamble, or rumination; not treat a follow-up question as a signal of prior error\n- `tengu_alder_wicket` \/ `CLAUDE_CODE_ALDER_WICKET`: accessor `nkc()` gates the `\"scope_fidelity\"` system prompt slot (`rl_`); when true, a second `# Delivering work` instruction block (a tighter variant) is added telling Claude to: interpret ambiguity as a careful colleague would; briefly state concerns then proceed as asked; finish the whole task not just the easy parts; stop short of actions clearly beyond what the request implies\n- All four use the shared helper `gYt(envVar, flagName)` which returns true if the env var is set, managed settings has the flag true, or `Ke()` returns true for the flag name\n\n**Evidence**\n\nAccessor functions and system prompt slots (search for `\"ekc()\"` near `Fa_()` for amber_astrolabe; `\"delivering_work_max\"` for bison_cairn; `\"overcorrection\"` for larch_cistern; `\"scope_fidelity\"` for alder_wicket)\n\n- Flag `tengu_bison_cairn`: Off in both readings (read for one account on one subscription tier against v2.1.217; this account: off, anonymous baseline: off, compiled default: not a boolean we can read) 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."}