{"version":"2.1.314","anchor":"permission-decision-reason-outsidewritesblocked-added","canonical_anchor":"permission-decision-reason-outsidewritesblocked-added","heading":"Permission records can now say a write outside was blocked","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/permission-decision-reason-outsidewritesblocked-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Permission records can now say a write outside was blocked\n\nClaude Code's internal permission reporting now sorts two more kinds of decision under a new label for blocked outside writes\n\n**Unclear.** Which permission decisions produce this label, and whether it reflects a new block on writes outside the project, is not clear.\n\n**What**\n\nWhen Claude Code decides whether an action is allowed, it records a reason for that decision in its internal usage reporting. Two more of those reasons are now grouped under a new label for writes outside that were blocked.\n\n**Why**\n\nThis changes how permission decisions are labelled in Claude Code's own reporting. It does not, by itself, change what Claude Code lets you do.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}