{"version":"2.1.280","anchor":"three-new-hidden-cli-settings-edit-commands-for-the-vs-code","canonical_anchor":"three-new-hidden-cli-settings-edit-commands-for-the-vs-code","heading":"New hidden CLI commands and APIs for editing skill, sandbox, and Chrome settings","tier":"use","area":"VSCode Extension","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/three-new-hidden-cli-settings-edit-commands-for-the-vs-code","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New hidden CLI commands and APIs for editing skill, sandbox, and Chrome settings\n\nThree new hidden claude CLI commands (and matching validated APIs) let the VS Code extension edit skill, sandbox, and Claude-in-Chrome settings\n\n**What**\n\n- Three new hidden `claude` subcommands were added: `edit-skill-overrides`, `edit-sandbox-settings`, and `edit-chrome-settings`, each reading one JSON edit from stdin.\n\n- They dispatch to new validated settings-write functions: one for per-skill invocation state (`on`, `name-only`, `user-invocable-only`, `off`, plus handles like unqualified name, aliases, and a bare-name-reserved flag), one for sandbox mode (`auto-allow`, `regular`, `disabled`, plus `allowUnsandboxedCommands`\/`excludeCommand`), and one for the Claude-in-Chrome default-enabled toggle (`claudeInChromeDefaultEnabled`).\n\n- Each write function validates its input with zod, checks for policy\/plugin\/author locks, and writes to local settings.\n\n**Why**\n\nThis gives the VS Code extension (and other callers) a supported, validated way to change skill, sandbox, and Claude-in-Chrome settings from the command line instead of writing to settings files directly.\n\n- Area: VSCode Extension\n- Names: `edit-permission-rules`, `edit-memory-settings`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}