{"version":"2.1.312","anchor":"artifacts-mcp-tools-auto-allow-for-routine-run-artifacts-an","canonical_anchor":"artifacts-mcp-tools-auto-allow-for-routine-run-artifacts-an","heading":"Artifact tools skip some permission prompts and ask when a comment is pending","tier":"notice","area":"Artifacts","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/artifacts-mcp-tools-auto-allow-for-routine-run-artifacts-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Artifact tools skip some permission prompts and ask when a comment is pending\n\nArtifact tools now allow a routine's new private artifact and repeat publishes without asking, but ask first when another person's comment may be pending\n\n**Unclear.** It is not clear which setting or feature check controls these new cases, or which artifact tools they apply to.\n\n**What**\n\nBefore one of Claude Code's artifact tools publishes a page, a permission check decides whether to go ahead or ask you first. That check now handles three cases differently:\n\n- A routine's new artifact that is private to you is allowed without asking. A routine is a task Claude Code runs on a schedule or a trigger.\n\n- Publishing again an artifact that was already published in the same session is allowed without asking.\n\n- If a comment on the artifact may not be yours, Claude Code always asks before going ahead.\n\nThe check also runs a publish step first.\n\n**Why**\n\nYou see fewer prompts for routine artifacts and repeat publishes. The forced prompt adds a safety stop when someone else's comment, which could contain instructions you did not write, is waiting on the artifact.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}