{"version":"2.1.319","anchor":"vs-code-card-message-approval-helper-gated-by-tengu-vscode-c","canonical_anchor":"vs-code-card-message-approval-helper-gated-by-tengu-vscode-c","heading":"VS Code sessions can approve actions through a host dialog","tier":"notice","area":"VS Code","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/vs-code-card-message-approval-helper-gated-by-tengu-vscode-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### VS Code sessions can approve actions through a host dialog\n\nIn VS Code, approvals can now go through a dialog shown by the editor, behind a switch that is on unless turned off remotely\n\n**Unclear.** What the new VS Code approval dialog looks like, and how the auto mode stop message now reaches you, is not stated.\n\n**What**\n\nWhen Claude Code runs inside VS Code, approvals can now go through a dialog shown by the host application rather than by Claude Code. This is behind a remote switch that is on unless it is switched off remotely, and applies only in VS Code.\n\nThe message Claude Code used to give when auto mode could not check actions and stopped after a run of refused actions is no longer produced in the same way. Claude Code now works out whether the session is in the desktop app or VS Code instead.\n\n**Why**\n\nApprovals in VS Code sessions move toward a dialog the editor shows itself.\n\n- Flag `tengu_vscode_card_message_approval`: Not enough to say (read for one account on one subscription tier against v2.1.319; 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: VS Code\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}