{"version":"2.1.275","anchor":"artifact-creation-reply-can-now-tag-urls-as-agent-scoped-ga","canonical_anchor":"artifact-creation-reply-can-now-tag-urls-as-agent-scoped-ga","heading":"Artifact creation reply can now tag URLs as agent-scoped, gated by a statsig flag","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/artifact-creation-reply-can-now-tag-urls-as-agent-scoped-ga","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Artifact creation reply can now tag URLs as agent-scoped, gated by a statsig flag\n\nArtifact creation replies can now mark a URL as agent-scoped, controlled by a gated flag\n\n**Unclear.** What agent-scoped actually changes about the URL or its access is not stated, and the gate `tengu_cobalt_plinth_medlar` is unread.\n\n**What**\n\nWhen Claude Code creates a new Artifact (a saved piece of generated content like a document or app), the message reporting success can now include `\"agent_scoped\"` when formatting the artifact's URL, depending on a check that is currently gated.\n\n**Why**\n\nThis lays groundwork for treating some artifact URLs as scoped to the agent that created them, rather than general-purpose links, though the gate controlling it has not been read for this account.\n\n- Flag `tengu_cobalt_plinth_medlar`: Not enough to say (read for one account on one subscription tier against v2.1.275; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}