{"version":"2.1.286","anchor":"tengu-stone-shell-check-removed-and-replaced-by-hardcoded-fa","canonical_anchor":"tengu-stone-shell-check-removed-and-replaced-by-hardcoded-fa","heading":"A server-controlled switch is now locked off in code","tier":"internal","area":"Remote Config","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/tengu-stone-shell-check-removed-and-replaced-by-hardcoded-fa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### A server-controlled switch is now locked off in code\n\nA check that used to ask the server whether to turn on a feature now always answers off, so no server setting can switch it on\n\n**Unclear.** Whether this check is the one that chose between file-based memory and memory tools, or guards something else.\n\n**What**\n\nA check in Claude Code used to ask the server for the flag tengu_stone_shell, falling back to off when the server sent nothing. That check now always answers off without asking. Whatever it guarded stays off for everyone, whatever the server sends.\n\nThat flag name earlier decided between file-based memory and the newer memory tools, before the decision moved to a differently named flag.\n\n**Why**\n\nA feature that could be switched on remotely can no longer be switched on in this build.\n\n- Flag `tengu_stone_shell`: Off in both readings (read for one account on one subscription tier against v2.1.286; 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: Remote Config\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}