{"version":"2.1.317","anchor":"new-vs-code-gate-tengu-vscode-start-second-try","canonical_anchor":"new-vs-code-gate-tengu-vscode-start-second-try","heading":"New remotely controlled setting in the VS Code extension","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/new-vs-code-gate-tengu-vscode-start-second-try","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### New remotely controlled setting in the VS Code extension\n\nThe VS Code settings gained a new setting that the server can switch, and nothing yet shows what it does\n\n**Unclear.** It is not known what this VS Code setting controls.\n\n**What**\n\nThe Claude Code extension for VS Code has a new setting that can be switched remotely by Anthropic's server. When the server sends no value, it falls back to on. Nothing so far shows what the setting controls.\n\n**Why**\n\nBecause it falls back to on, it is likely active unless the server turns it off. There is nothing you can do with it until it shows what it controls.\n\n- Flag `tengu_vscode_start_second_try`: 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: on) 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: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}