Workflow prompt provenance now read from CLAUDE_CODE_WORKFLOW_PROMPT_PROVENANCE and made synchronous
The function that used to read the CLAUDE_CODE_DAPPER_LAGOON environment variable (falling back to a gate called MOo) now reads a new environment variable, CLAUDE_CODE_WORKFLOW_PROMPT_PROVENANCE, falling back to a gate called tengu_bubbly_harbor, which defaults to true. Two places in the workflow engine that used to await this check now call it directly, since it no longer needs to run asynchronously.
The flag server is currently returning this gate as on for both this site's account and the anonymous baseline, though no reading has been taken specifically under this release yet. Renaming the environment variable and making the check synchronous suggests this first-party detection logic was reworked and simplified.
tengu_bubbly_harbor On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.277: on
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.277. It isn't a statement about your account. What a flag value here can and cannot tell you
New in this build: tengu_bubbly_harbor