Unclear What triggers each writer (e.g. a specific command or automatic behavior) is not stated in the finding.
What
- Three new hidden
claudesubcommands were added:edit-skill-overrides,edit-sandbox-settings, andedit-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, plusallowUnsandboxedCommands/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.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What triggers each writer (e.g. a specific command or automatic behavior) is not stated in the finding.