{"version":"2.1.268","anchor":"new-bridge-dialog-for-tools-that-would-read-outside-the-allo","canonical_anchor":"new-bridge-dialog-for-tools-that-would-read-outside-the-allo","heading":"New bridge dialog for tools that would read outside the allow-list ('block outside reads')","tier":"soon","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/new-bridge-dialog-for-tools-that-would-read-outside-the-allo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### New bridge dialog for tools that would read outside the allow-list ('block outside reads')\n\nA new confirmation dialog appears when a tool tries to read a file outside the allowed list\n\n**Unclear.** Whether this dialog is active for any given account depends on the tengu_compressed_river gate, which is unread for this account, so nothing can be said about whether it is switched on.\n\n**What**\n\nWhen a tool tries to read a file path that falls outside your allowed-reads list, Claude Code can now show a dedicated dialog offering to allow it, block it, or ask again later, instead of just denying it outright. The permission system now carries a flag, `offersBlockOutsideReads`, that decides whether this new dialog appears, and denying through it records that the read was blocked for being outside the allow-list.\n\n**Why**\n\nThis gives you a clearer, more specific choice when a tool asks to read something outside the paths you've allowed, rather than a generic denial.\n\n- Flag `tengu_compressed_river`: Not enough to say (read for one account on one subscription tier against v2.1.268; this account: no value returned, anonymous baseline: no value returned, compiled default: on)\n- Area: Permissions\n- Names: `offersBlockOutsideReads`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}