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
Home / Reference / Settings keys

allowUnsandboxedCommands

setting never mined JSON

A Claude Code settings key, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.

Windows sandbox decisions now hinge on configured strict mode rather than a runtime toggle.

Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.234.

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 149on this box, as of v2.1.308
Written about v2.0.30 first named in a changelog, 30 Oct 2025

In the changelogs

13

Releases whose published page names allowUnsandboxedCommands.

  1. v2.1.285
    Turning off unsandboxed commands is honored from an additional settings source

    Setting allowUnsandboxedCommands to false is now also read through a second settings lookup

    found in this entry's text, named in this entry

  2. v2.1.285
    New descriptions of how settings files combine for sandbox rules

    New text explains that project settings cannot re-open paths denied for reading, and that some project-level network values are ignored

    found in this entry's text

  3. v2.1.285
    Sandbox lock on unsandboxed commands now described as covering your own settings

    overrides_locked is now described as true when allowUnsandboxedCommands: false comes from a --settings file or user settings

    found in this entry's text, named in this entry

  4. v2.1.285
    Sandbox settings carry clearer descriptions

    Descriptions for sandbox settings are fuller, including that sandbox.enabled defaults to false; behaviour is unchanged

    found in this entry's text

  5. v2.1.282
    Repositories can no longer exempt commands from a sandbox an admin has locked down

    When running commands outside the sandbox is forbidden, sandbox.excludedCommands entries in a project's own settings files are ignored

    found in this entry's text

  6. v2.1.282
    Sandbox exclusions now fail clearly when user settings are turned off

    Adding a sandbox command exclusion now fails with an explanation when user settings are off, instead of reporting a success that did nothing

    found in this entry's text

  7. v2.1.282
    Excluding a command from the sandbox can now be refused under a strict setup

    When commands outside the sandbox are forbidden, excluding a command is saved to user settings or refused, not saved to local settings

    found in this entry's text, named in this entry

  8. v2.1.280
    Three new hidden CLI settings-edit commands for the VS Code extension

    Three new hidden CLI commands let the VS Code extension edit skill, sandbox, and Chrome settings

    found in this entry's text

  9. v2.1.280
    New skill-state, sandbox, and Claude-in-Chrome settings-write APIs

    Three new internal settings-write functions handle per-skill state, sandbox mode, and Claude-in-Chrome default-enabled toggle

    found in this entry's text

  10. v2.1.251
    Eval runs that grant a shell tool now refuse to run without a sandbox

    Eval runs with a shell tool refuse to start without a sandbox, and hide your credential files.

    found in this entry's text

  11. v2.1.234
    Windows sandbox decisions keyed on configured strict mode

    Windows sandbox decisions now hinge on configured strict mode rather than a runtime toggle.

    named in this entry, found in this entry's text

  12. v2.1.98
  13. v2.0.30
    Enhanced Sandbox Security Policy

    found in this entry's text

First cited

2

The earliest release whose published evidence quoted allowUnsandboxedCommands was v2.1.285, 29 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

ReleaseDateThe span that was quoted
v2.1.28529 Sep 2026allowUnsandboxedCommands
v2.1.28529 Sep 2026held closed (allowUnsandboxedCommands: false) by a --settings file or user settings

Presence across releases

0

The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.

Feedback