{"version":"2.1.292","anchor":"publish-without-asking-limited-to-fresh-page-creation","canonical_anchor":"publish-without-asking-limited-to-fresh-page-creation","heading":"Publishing an artifact without asking is limited to creating a new one","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/publish-without-asking-limited-to-fresh-page-creation","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Publishing an artifact without asking is limited to creating a new one\n\nA publish Claude Code makes without asking can now only create a new artifact; anything else is refused and later publishes need permission\n\n**What**\n\nClaude Code can sometimes publish an artifact, a page it puts online, without asking you first. That kind of publish may now only create a new artifact. It is refused if it does any of these:\n\n- names a url\n\n- sets capabilities\n\n- sets a contract\n\n- uses force\n\n- removes files\n\n- includes live files\n\nWhen that happens, nothing is published, and every later publish in the same session (one Claude Code conversation) goes through the usual permission check.\n\n**Why**\n\nThis narrows what can be published while you are not being asked, so an unattended publish can only create a fresh page.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}