{"version":"2.1.221","anchor":"plan-mode-now-needs-a-real-human-for-artifact-page-data-read","canonical_anchor":"plan-mode-now-needs-a-real-human-for-artifact-page-data-read","heading":"Plan mode now needs a real human for artifact page-data reads and publishes","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/plan-mode-now-needs-a-real-human-for-artifact-page-data-read","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Plan mode now needs a real human for artifact page-data reads and publishes\n\nIn plan mode, artifact page reads and publishes always need you to approve them yourself.\n\n**What**\n\nThe first artifact page-data read and any artifact publish made from plan mode can no longer be approved automatically, and approval granted in plan mode is stored as a distinct human approval rather than reused as a generic session grant.\n\n**Details**\n\n- Both call paths are marked as not approvable by the auto-permission classifier.\n- A hidden input key records that the request originated in plan mode, so the session-wide approval is persisted separately as a human approval.\n- When plan mode has no usable consent surface, publish is denied outright; the page-data read still asks, with an explanation that nobody is present to answer it.\n\n**Evidence**\n\n`Plan-mode publish egress requires a live human consent surface`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}