Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.280 ·

New hidden CLI commands and APIs for editing skill, sandbox, and Chrome settings

Three new hidden claude CLI commands (and matching validated APIs) let the VS Code extension edit skill, sandbox, and Claude-in-Chrome settings

Group of 2 Use it now Internal Changes
JSON All of v2.1.280
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SettingsArea: what it touches
Internal ChangesKind: in v2.1.280,
What probably matters to youSection of the release

Unclear What triggers each writer (e.g. a specific command or automatic behavior) is not stated in the finding.

What

  • Three new hidden claude subcommands were added: edit-skill-overrides, edit-sandbox-settings, and edit-chrome-settings, each reading one JSON edit from stdin.
  • 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).
  • Each write function validates its input with zod, checks for policy/plugin/author locks, and writes to local settings.

Why

This 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.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat triggers each writer (e.g. a specific command or automatic behavior) is not stated in the finding.

See this entry in the whole of v2.1.280 →

Feedback