{"version":"2.1.321","anchor":"tengu-precious-ember-widened-by-a-platformauth-condition","canonical_anchor":"tengu-precious-ember-widened-by-a-platformauth-condition","heading":"A remotely controlled behaviour now applies in more kinds of setup","tier":"internal","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/tengu-precious-ember-widened-by-a-platformauth-condition","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### A remotely controlled behaviour now applies in more kinds of setup\n\nThe behaviour behind one remote setting now applies in more environments, because one of its two conditions now has an alternative\n\n**Unclear.** Which environments and sign-in methods the widened condition now covers, and what the behaviour itself is, are not known.\n\n**What**\n\nClaude Code checks the remote setting `tengu_precious_ember` together with one further condition about your setup before a particular behaviour applies. The setting itself still falls back to on unless it is switched off remotely. What changed is the further condition: it used to be a single check, and it is now met if either that kind of check passes or a combination of three other checks about your platform and sign-in method passes. The behaviour therefore applies in more environments than before.\n\n**Why**\n\nBecause the setting is on by default, this extra condition is what decides who gets the behaviour, so widening it changes who is affected.\n\n- Flag `tengu_precious_ember`: Not enough to say (read for one account on one subscription tier against v2.1.321; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}