{"version":"2.1.211","anchor":"claude-design-permanent-durable-project-write-grants","canonical_anchor":"claude-design-permanent-durable-project-write-grants","heading":"Claude Design: Permanent Durable Project Write Grants","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.211\/e\/claude-design-permanent-durable-project-write-grants","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.211","markdown":"### Claude Design: Permanent Durable Project Write Grants\n\n**What**\n\nThe approval model for Claude Design project writes is fundamentally reworked. The old time-limited \"4-hour project grant\" from `finalize_plan scope:\"project\"` is replaced by a permanent durable grant that persists until explicitly revoked at claude.ai\/design settings.\n\n**Details**\n\n- The first write to a project triggers a one-time interactive approval. After approval, Claude can write to any file in the project without further prompts until revoked.\n- The approval approval message now reads: \"Approving writes the listed files now, and lets Claude write to ANY file in the project\u2026\" rather than the previous \"without another prompt for up to 4 hours\".\n- Grants are revocable at any time via claude.ai\/design settings.\n- `finalize_plan scope:\"project\"` is now deprecated \u2014 the client returns a deny message directing callers to use direct writes instead.\n- `copy_files` without a `plan_token` is now always rejected (requires `finalize_plan` with explicit destination paths).\n- Write batches that are too large to display in the approval dialog are rejected and must be split or issued via `finalize_plan`.\n- Projects shared from another organization cannot receive durable grants \u2014 those require per-batch `plan_token` flows.\n- Durable grants are not available in non-interactive sessions, plan mode, subagent sessions, or PermissionRequest-hook contexts.\n\n**Evidence**\n\nReplaced approval text (search for `\"first write under a project grant\"`)"}