Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.242 Home All releases olderv2.1.241 v2.1.243newer
Claude Code v2.1.242

Starting an Artifact from a type in a cloud session, behind a second gate that is off

Not switched on
Useful2 Signal4
Artifacts Notable not in their notes

Creating an artifact from a type inside a cloud session sits behind a second switch, off.

CLAUDE_CODE_ARTIFACT_TYPE_CLOUD_CREATE or its flag would unlock cloud type creation; both fall back off.

Feature flag
tengu_cobalt_plinth_larch Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.242: not a boolean we can read

tengu_cobalt_plinth_hazel Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.242: not a boolean we can read

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

CLAUDE_CODE_ARTIFACT_TYPESCLAUDE_CODE_ARTIFACT_TYPE_CLOUD_CREATE
What

Artifact types (listing and describing available types, filtering by type, both treated as read-only for permissions) remain behind CLAUDE_CODE_ARTIFACT_TYPES or the flag tengu_cobalt_plinth_larch. New here is a second switch specifically for creating an Artifact from a type while in a cloud session: CLAUDE_CODE_ARTIFACT_TYPE_CLOUD_CREATE or the flag tengu_cobalt_plinth_hazel. Both fall back to off, so on a stock cloud session this is closed.

Details
  • Local sessions allow type-based creation unconditionally; only remote sessions need the second gate, on top of types being enabled at all.
  • The decision is frozen once per session and then selects between the working prompt and the refusal wording.
  • When closed, publishing with a type URL returns a sentence aimed at the model telling it not to retry there and to give the user the type's link instead.
Evidence

Starting a new Artifact from a type isn't available in this cloud session right now, so nothing was created; do not retry here., tengu_cobalt_plinth_hazel

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.242 →