{"version":"2.1.317","anchor":"tengu-foamy-heron-check-generalised-to-a-flag-name-parameter","canonical_anchor":"tengu-foamy-heron-check-generalised-to-a-flag-name-parameter","heading":"A second remote switch now shares an existing switch's check","tier":"internal","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/tengu-foamy-heron-check-generalised-to-a-flag-name-parameter","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### A second remote switch now shares an existing switch's check\n\nClaude Code now checks two remote switches the same way, and both are treated as on when the server sends nothing\n\n**Unclear.** What either switch controls is not stated.\n\n**What**\n\nClaude Code now checks two remote switches, `tengu_foamy_heron` and `tengu_deep_locket`, the same way. Both are treated as on when the server sends nothing.\n\n**Why**\n\nThe second switch, `tengu_deep_locket`, did not exist before and follows the same rules as the first.\n\n- Flag `tengu_foamy_heron`: Not enough to say (read for one account on one subscription tier against v2.1.317; this account: no value returned, anonymous baseline: no value returned, 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"}