{"version":"2.1.269","anchor":"sandboxed-command-deny-message-and-blockoutsidereads-flow-re","canonical_anchor":"sandboxed-command-deny-message-and-blockoutsidereads-flow-re","heading":"Sandboxed-command deny message and blockOutsideReads flow renamed\/reworked","tier":"internal","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/sandboxed-command-deny-message-and-blockoutsidereads-flow-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Sandboxed-command deny message and blockOutsideReads flow renamed\/reworked\n\nInternal rework of the sandbox 'reads outside working directory' deny dialog, same message and behavior\n\n**Unclear.** what the new host_dialog tag is used for beyond being passed into the dialog flow\n\n**What**\n\nThe code path that shows the deny message for `permissions.blockReadsOutsideWorkingDirectories` (which blocks file tools from reading outside your working directories) was internally restructured, and a new `host_dialog` tag is now passed along when the dialog is shown. The message itself, which tells you to add the directory with `\/add-dir`, is unchanged.\n\n**Why**\n\nThis is an internal refactor with no visible change in behavior; the same deny message and recovery path (`\/add-dir`) still apply when a tool tries to read outside your allowed directories.\n\n- Area: Sandbox\n- Names: `\/add-dir`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}