{"version":"2.1.323","anchor":"read-permission-check-passes-a-forthemodelhere-flag","canonical_anchor":"read-permission-check-passes-a-forthemodelhere-flag","heading":"Blocked file reads now give a reason that depends on your read-block setting","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/read-permission-check-passes-a-forthemodelhere-flag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Blocked file reads now give a reason that depends on your read-block setting\n\nThe reason Claude Code gives for blocking a file read now changes depending on the `blockReadsOutsideWorkingDirectories` setting\n\n**What**\n\nClaude Code checks whether it is allowed to read a file before reading it. When that check blocks a read, Claude Code gives a reason. That reason used to be the same every time. It now differs depending on the `blockReadsOutsideWorkingDirectories` setting.\n\n**Why**\n\nThe reason for a blocked read now reflects your `blockReadsOutsideWorkingDirectories` setting, which blocks reads outside your working folders, instead of always being the same message.\n\n- Area: Permissions\n- Names: `blockReadsOutsideWorkingDirectories`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}