{"version":"2.1.268","anchor":"read-outside-working-directory-prompt-text-centralized-behin","canonical_anchor":"read-outside-working-directory-prompt-text-centralized-behin","heading":"Read-outside-working-directory prompt text centralized behind a typed dialog kind","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/read-outside-working-directory-prompt-text-centralized-behin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Read-outside-working-directory prompt text centralized behind a typed dialog kind\n\nThe 'Read outside the working directories?' permission prompt is now built from a dedicated dialog descriptor\n\n**What**\n\nThe permission prompt Claude Code shows when it wants to read a file outside your project's working directories ('Read outside the working directories?') is now generated from a dedicated, named dialog descriptor (`auto_mode_outside_reads`) with a fixed set of choices: allow, block, or ask again. Previously this prompt and its explanatory text were assembled inline in the code, rather than from a single reusable descriptor.\n\n**Why**\n\nThis is mostly a code organization change, centralizing how this specific permission prompt is built. For users, the visible prompt and its options (like 'Yes, keep allowing reads outside the working directories') stay conceptually the same.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}