{"version":"2.1.292","anchor":"remote-config-flag-rename-tengu-purring-yeti-to-tengu-quirk","canonical_anchor":"remote-config-flag-rename-tengu-purring-yeti-to-tengu-quirk","heading":"A remotely configured list is read under a new server name","tier":"internal","area":"Remote Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/remote-config-flag-rename-tengu-purring-yeti-to-tengu-quirk","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### A remotely configured list is read under a new server name\n\nA list Claude Code fetches from its remote configuration is now read under a different name, so values set under the old name no longer apply\n\n**Unclear.** It is not stated what this list controls in Claude Code.\n\n**What**\n\nClaude Code reads some settings from a remote configuration service, which lets the server adjust its behaviour without a new release. One of these settings, a list of values, is now read under a different name than before. If the server sends nothing for it, Claude Code falls back to the same built-in default as in the previous build.\n\n**Why**\n\nAny value the server had set under the old name no longer reaches Claude Code. Only the new name now controls this list.\n\n- Flag `tengu_quirky_kazoo`: Not enough to say (read for one account on one subscription tier against v2.1.292; 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: Remote Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}