{"version":"2.1.323","anchor":"runtime-settings-cant-flip-blockfiletoolreadsoutsideworking","canonical_anchor":"runtime-settings-cant-flip-blockfiletoolreadsoutsideworking","heading":"Blocking file reads outside your project can only be set at launch","tier":"notice","area":"Permissions","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/runtime-settings-cant-flip-blockfiletoolreadsoutsideworking","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Blocking file reads outside your project can only be set at launch\n\npermissions.blockFileToolReadsOutsideWorkingDirectories is now ignored when sent to a running session and counts only in --settings at launch\n\n**What**\n\nThe permission `permissions.blockFileToolReadsOutsideWorkingDirectories` is now ignored if it arrives in settings sent to a session that is already running. It stops Claude's file tools from reading outside your working directories. Claude Code logs a message saying it was ignored. The permission only takes effect when it is passed in `--settings` when Claude Code starts.\n\nClaude Code also now records an event when a session leaves bypass-permissions mode, the mode where Claude acts without asking you first.\n\n**Why**\n\nThis keeps the file-read restriction from being switched in the middle of a session. If you depend on it, pass it in `--settings` when you launch Claude Code.\n\n- Area: Permissions\n- Names: `permissions.blockFileToolReadsOutsideWorkingDirectories`, `--settings`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: yes"}