{"version":"2.1.290","anchor":"permission-engine-plan-floor-and-own-made-delete-handling","canonical_anchor":"permission-engine-plan-floor-and-own-made-delete-handling","heading":"Permission checks gain a plan-mode reason, an own_record consent reason and an exception for self-made deletes","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/permission-engine-plan-floor-and-own-made-delete-handling","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Permission checks gain a plan-mode reason, an own_record consent reason and an exception for self-made deletes\n\nPermission decisions now give a reason under plan mode limits and under `own_record`, and deletes of things the session made can skip a safety block\n\n**Unclear.** It is not clear what controls the self-made delete exception or when the unattended `own_record` behaviour applies.\n\n**What**\n\nThe rules that decide when Claude Code asks you for permission (asks you to approve an action before it runs) have changed in a few ways:\n\n- A permission request from a server that falls under the plan-mode limit is now reported with its own plan-mode reason.\n\n- The `own_record` setting for unattended sessions (sessions running with nobody present to answer prompts) can now return a consent reason.\n\n- Deleting something that the session itself created can now go ahead even when the automatic safety check would otherwise block it.\n\nPermission requests also carry an added explanation for paths reached through MCP servers, which are add-on tool servers.\n\n**Why**\n\nThese changes affect when you are prompted for permission and when an action is allowed without a prompt.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}