The artifact feature no longer defaults to off. With no remote-config value present, artifacts are enabled when the account's auth source is unset, prosumer_oauth, or no_auth, and stay off for every other auth shape. Remote config can still turn it on or off in either direction.
- The gate is
tengu_cobalt_plinth; only its fallback changed, from a hard false to the auth-source test. - Enterprise and API-key style logins keep the old off-by-default behaviour unless remote config says otherwise.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_cobalt_plinth 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.234: not a boolean we can read
Read once, for one account on one subscription tier, against v2.1.234. 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.
The code path no longer asks a flag before it runs.