Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial
Home / Reference / Settings keys

permissions.blockFileToolReadsOutsideWorkingDirectories

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.

permissions.blockFileToolReadsOutsideWorkingDirectories stops Claude's file tools reading outside the folders Claude Code was launched with

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

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 162on this box, as of v2.1.323
Written about v2.1.323 first named in a changelog, 12 Nov 2026

In the changelogs

9

Releases whose published page names permissions.blockFileToolReadsOutsideWorkingDirectories.

  1. v2.1.323
    New setting limits file tool reads to the folders Claude Code started in

    permissions.blockFileToolReadsOutsideWorkingDirectories stops Claude's file tools reading outside the folders Claude Code was launched with

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

  2. v2.1.323
    New setting to block file tools from reading outside your project

    permissions.blockFileToolReadsOutsideWorkingDirectories can stop file reads outside your working directories from being allowed automatically

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

  3. v2.1.323
    ExitWorktree refuses to leave or remove a worktree when folder limits apply

    ExitWorktree now stops rather than return outside the launch folders, or remove some worktrees, when the matching permission settings are on

    found in this entry's text

  4. v2.1.323
    Session info now reports whether reads and writes outside your folders are blocked

    Session info now says whether file reads and writes outside the working directories are blocked, and the sandbox also honours a new read-blocking setting

    found in this entry's text

  5. v2.1.323
    Blocking file reads outside your project can only be set at launch

    permissions.blockFileToolReadsOutsideWorkingDirectories is now ignored when sent to a running session and counts only in --settings at launch

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

  6. v2.1.323
    Teammates stay in the main window when reads outside the project are blocked

    With permissions.blockFileToolReadsOutsideWorkingDirectories on, teammates always run in-process instead of in tmux or iTerm2 panes

    found in this entry's text

  7. v2.1.323
    Warnings when read-fence settings are put where they are ignored

    Claude Code now warns when permissions.blockFileToolReadsOutsideWorkingDirectories and related keys are set in a settings file, where they are ignored

    found in this entry's text

  8. v2.1.323
    --await-claim no longer starts when file reads are limited to launch folders

    Starting with --await-claim now fails if permissions.blockFileToolReadsOutsideWorkingDirectories is on

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

  9. v2.1.323
    EnterWorktree now stays inside the folders allowed at launch

    With file reads limited to launch folders, EnterWorktree refuses worktrees outside them and moves the session back if a later check fails

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

First cited

5

The earliest release whose published evidence quoted permissions.blockFileToolReadsOutsideWorkingDirectories was v2.1.323, 12 Nov 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.32312 Nov 2026Error: --await-claim cannot be used with permissions.blockFileToolReadsOutsideWorkingDirectories: that setting admits only the folders given at the launch, and a spare is launched before its project is known. Start the session in its project's folder instead.
v2.1.32312 Nov 2026Reads outside the working directories are blocked (permissions.blockFileToolReadsOutsideWorkingDirectories).
v2.1.32312 Nov 2026[BackendRegistry] isInProcessEnabled: true (permissions.blockFileToolReadsOutsideWorkingDirectories)
v2.1.32312 Nov 2026permissions.blockFileToolReadsOutsideWorkingDirectories is ignored in settings sent to a running session: it counts only in --settings at the launch
v2.1.32312 Nov 2026permissions.blockFileToolReadsOutsideWorkingDirectories: ${s.names.join(", ")} was changed by neither the launch nor --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