{"version":"2.1.318","anchor":"tengu-serene-curry-fallback-changed-from-false-to-a-computed","canonical_anchor":"tengu-serene-curry-fallback-changed-from-false-to-a-computed","heading":"A remote switch's fallback now depends on how Claude Code was started","tier":"internal","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/tengu-serene-curry-fallback-changed-from-false-to-a-computed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### A remote switch's fallback now depends on how Claude Code was started\n\nWhen the server sends nothing, a remote switch no longer always falls back to off and may be on depending on how Claude Code was started\n\n**Unclear.** It is not clear which ways of starting Claude Code get an on fallback, or what the switch controls.\n\n**What**\n\nWhen the server sends no value for the remote switch `tengu_serene_curry`, its fallback is no longer always off. The fallback is now worked out from how Claude Code was started. For this site's account and for an anonymous check, the server answered off.\n\n**Why**\n\nIn some ways of starting Claude Code, the part this switch guards may now run when the server sends nothing.\n\n- Flag `tengu_serene_curry`: Off in both readings (read for one account on one subscription tier against v2.1.318; 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.\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}