Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.275 ·

Artifact creation reply can now tag URLs as agent-scoped, gated by a statsig flag

Artifact creation replies can now mark a URL as agent-scoped, controlled by a gated flag

TierNothing to try yethow much it should matter to you
Useful1my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaArtifactswhat it touches
KindIn Developmentin v2.1.275,
Nothing to try yet

Artifact creation replies can now mark a URL as agent-scoped, controlled by a gated flag

What

When 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.

Why

This 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.

Read from
Feature flag
tengu_cobalt_plinth_medlar Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.275: 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.

Read once, for one account on one subscription tier, against v2.1.275. It isn't a statement about your account. What a flag value here can and cannot tell you

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat agent-scoped actually changes about the URL or its access is not stated, and the gate `tengu_cobalt_plinth_medlar` is unread.

See this entry in the whole of v2.1.275 →