{"version":"2.1.221","anchor":"read-page-data-needs-a-human-approval-in-plan-mode","canonical_anchor":"read-page-data-needs-a-human-approval-in-plan-mode","heading":"read_page_data needs a human approval in plan mode","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/read-page-data-needs-a-human-approval-in-plan-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### read_page_data needs a human approval in plan mode\n\nIn plan mode, reading artifact page data now needs your actual approval, not an auto-approval.\n\n**What**\n\nApproval for the artifact read_page_data action is tracked in two separate app-state flags, and in plan mode the tool auto-allows only when the human-approved flag is set.\n\n**Details**\n\n- a plan-mode auto-approval no longer carries over into the human-approved flag\n- checkLiveEditPermissions now receives the plan-consent denier and the permission context\n- outside plan mode the existing approval flag still applies\n\n**Evidence**\n\n`artifactReadPageDataHumanApproved`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}