Source Intelligence
Follow Discord

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.236 Home All releases ←olderv2.1.235 v2.1.237newer→
Claude Code v2.1.236

Artifact types (templates and starters), built end to end and off by default

Not switched on
Useful2 Signal5
Artifacts Notable not in their notes

You could start a private artifact from a published template, but two server switches keep it shut here.

Artifact types (template-backed starters with a type_url parameter) are built end to end but sit behind two server flags that default 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.236: on

tengu_cobalt_plinth_bracken 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.236: on

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

type_urlCLAUDE_CODE_ARTIFACT_TYPES
What

A new publish mode lets Claude start a private artifact on claude.ai from a published "Artifact type", a template whose page and settings are fixed by its publisher: pass type_url and your own files land alongside the type's. It is held shut by two independently gated server flags, both defaulting off, plus a local-only check, so nothing here is reachable in this build without server config. Reading and publishing into an artifact that already came from a type are unaffected by these gates; only creation from a type is suppressed.

Details
  • Creation needs both tengu_cobalt_plinth_larch (or the environment variable CLAUDE_CODE_ARTIFACT_TYPES) and tengu_cobalt_plinth_bracken; all three names are new in this build.
  • Both flags are resolved once when the tool schema is built and frozen for the session, so they cannot change mid-session. With them off, type_url is not in the schema at all and the tool refuses with a message that artifact types are not enabled in this session.
  • The create capability is computed as types-on AND the environment variable CLAUDE_CODE_REMOTE not being set, so a remote or web session never sees type_url even with both flags on.
  • Creation posts to /api/frame/types/<slug>/create with one retry that honours retry-after on 409 and 429; failures include recovery text for the case where the artifact was created but the file publish failed.
  • type_url cannot be combined with url, pr_review, capabilities, contract, lang or force, and creating twice from the same type in one session is refused.
  • Results distinguish your own files from the type's files, and the type's page is injected as untrusted content inside its own wrapper.
  • Plan mode and Cowork frames, the shared-workspace surface, each have their own deny paths, and new analytics record the create with counts of own files and type files.
Evidence

Create a new private Artifact on claude.ai from an existing Artifact type, created_from_type, tengu_cobalt_plinth_larch, a publish with \type_url\ always creates a new Artifact whose page and settings come from the type \u2014 remove \url\, \pr_review\, \capabilities\, \contract\, \lang\, and \force\`, tengu_cobalt_plinth_bracken, Artifact types: To start a new Artifact from a published Artifact type (people may call one a template or a starter), pass \type_url\ (the type's link), typeLocked: n.data.type != null && typeof n.data.type === "object", type_locked, Artifact types are not enabled in this session, creating an Artifact from an Artifact type (\type_url\) is not available in this session — remove \type_url\, CLAUDE_CODE_ARTIFACT_TYPES, CLAUDE_CODE_REMOTE`

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.236 →