{"version":"2.1.311","anchor":"tengu-wiggly-locket-check-added","canonical_anchor":"tengu-wiggly-locket-check-added","heading":"New remotely controlled check with no visible effect yet","tier":"soon","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/tengu-wiggly-locket-check-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### New remotely controlled check with no visible effect yet\n\nA new check tied to a server-controlled switch passes by default; what it guards is not yet clear\n\n**Unclear.** What feature this check guards is not known.\n\n**What**\n\nClaude Code has a new check tied to a server-controlled switch, `tengu_wiggly_locket`, which falls back to off when the server sends nothing. The check passes unless the switch is exactly on, and it also passes when any of three other conditions holds.\n\n**Why**\n\nWith the fallback in place the check passes, so nothing it guards is held back by default.\n\n- Flag `tengu_wiggly_locket`: Not enough to say (read for one account on one subscription tier against v2.1.311; this account: no value returned, anonymous baseline: no value returned, compiled default: off) 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: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}