{"version":"2.1.248","anchor":"publishes-can-skip-the-prompt-when-the-content-matches-an-al","canonical_anchor":"publishes-can-skip-the-prompt-when-the-content-matches-an-al","heading":"Publishes can skip the prompt when the content matches an already-approved edit","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/publishes-can-skip-the-prompt-when-the-content-matches-an-al","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Publishes can skip the prompt when the content matches an already-approved edit\n\nPublishing skips the permission prompt when the bytes match an edit you already approved.\n\n**What**\n\nPublishing an artifact no longer prompts for permission when the bytes being published exactly match a staged automatic edit you already approved. The permission check returns an allow instead of asking.\n\n**Details**\n\n- Requires the SHA-256 of the pending source to equal the recorded hash on the staged auto-reaction edit, plus a decision reason of either \"other\" or a safety check the classifier can approve.\n- An additional check on the tool and its input also gates this path; when any part fails, the normal ask flow runs unchanged.\n- Allowed publishes log an analytics event marking the publish as tool-allowed.\n\n**Evidence**\n\n`b(\"artifact_comments_autoreact\", { edit_publish_tool_allowed: !0 })`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}