{"version":"2.1.234","anchor":"artifacts-now-default-on-for-consumer-oauth-logins","canonical_anchor":"artifacts-now-default-on-for-consumer-oauth-logins","heading":"Artifacts now default on for consumer OAuth logins","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/artifacts-now-default-on-for-consumer-oauth-logins","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Artifacts now default on for consumer OAuth logins\n\nArtifacts are now on by default for consumer OAuth logins instead of off.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- The gate is `tengu_cobalt_plinth`; only its fallback changed, from a hard false to the auth-source test.\n- Enterprise and API-key style logins keep the old off-by-default behaviour unless remote config says otherwise.\n\n**Evidence**\n\n`tengu_cobalt_plinth`\n\n- Flag `tengu_cobalt_plinth`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.234; this account: on, anonymous baseline: on, compiled default: not a boolean we can read)\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5"}