{"version":"2.1.292","anchor":"routine-first-publish-of-artifacts-without-being-asked-is-tr","canonical_anchor":"routine-first-publish-of-artifacts-without-being-asked-is-tr","heading":"Routines that publish an artifact unasked can mark their run","tier":"internal","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/routine-first-publish-of-artifacts-without-being-asked-is-tr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Routines that publish an artifact unasked can mark their run\n\nClaude Code now records when a routine first publishes an artifact without being asked, and can mark that run as tainted\n\n**Unclear.** What marking a routine run as tainted changes for the user is not stated.\n\n**What**\n\nWhen a routine publishes an artifact for the first time without being asked to, Claude Code now records it. The outcome decides what happens next:\n\n- owner-only, or refused before sending: nothing further\n\n- any other known outcome: the run is marked as tainted\n\n- an unknown outcome: the run is marked and an error is logged saying the publish was not owner-only\n\n**Why**\n\nThis looks like a guard on routines sharing artifacts with people other than their owner.\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}