{"version":"2.1.221","anchor":"design-tool-clearer-refusal-when-a-project-write-grant-is-mi","canonical_anchor":"design-tool-clearer-refusal-when-a-project-write-grant-is-mi","heading":"Design tool: clearer refusal when a project write grant is missing in non-interactive sessions","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/design-tool-clearer-refusal-when-a-project-write-grant-is-mi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Design tool: clearer refusal when a project write grant is missing in non-interactive sessions\n\nDesign tool now explains exactly how to get write access when running without an interactive session.\n\n**What**\n\nCalling write_files or create_support_js without an active project write grant in a non-interactive session now returns a specific error explaining the route forward.\n\n**Details**\n\n- The message directs the caller to use finalize_plan with writes and to pass the plan_token.\n- It states that a durable grant must be approved from an interactive session.\n- Carries error code design_tool_needs_project_grant_non_interactive.\n\n**Evidence**\n\n`design_tool_needs_project_grant_non_interactive`\n\n- Area: Artifacts\n- Names: `finalize_plan`, `plan_token`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}