Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.265 ·

Artifacts now flag when they're shared from another organization

Claude Code now marks and explains artifacts that were shared with you from outside your own organization

TierYou'll noticehow much it should matter to you
Useful3my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaArtifactswhat it touches
KindImprovementsin v2.1.265,
Group of 2 You'll notice

Claude Code now marks and explains artifacts that were shared with you from outside your own organization

What

  • Artifact reads now track whether an artifact is external, meaning it was shared from a different organization than your own, and show distinct messaging for that case ("shared with you from another organization" / noting the author is outside your organization), separate from the existing public/owner/writer distinctions.
  • When artifact data comes back marked with mode external, an explicit external: true flag is now passed along through both the artifact-read and comments-list code paths, rather than being dropped.
  • A new typePage parameter (defaulting to "none") controls whether the artifact's "type contract" text (a description of the artifact's structure) is fetched and included when reading it, so that text isn't refetched on every single read.

Why

This makes it clearer to users and to Claude when an artifact originated outside their own organization, and avoids unnecessary repeated fetching of type-contract text on every artifact read.

Read from
Feature flag
tengu_cobalt_plinth_larch 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: off · compiled default in v2.1.265: off

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

See this entry in the whole of v2.1.265 →

Feedback