{"version":"2.1.236","anchor":"artifact-types-templates-and-starters-built-end-to-end-and-o","canonical_anchor":"artifact-types-templates-and-starters-built-end-to-end-and-o","heading":"Artifact types (templates and starters), built end to end and off by default","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/artifact-types-templates-and-starters-built-end-to-end-and-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Artifact types (templates and starters), built end to end and off by default\n\nYou could start a private artifact from a published template, but two server switches keep it shut here.\n\n**What**\n\nA 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.\n\n**Details**\n\n- 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.\n- 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.\n- 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.\n- 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.\n- `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.\n- Results distinguish your own files from the type's files, and the type's page is injected as untrusted content inside its own wrapper.\n- 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.\n\n**Evidence**\n\n`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 \u2014 remove \\`type_url\\``, `CLAUDE_CODE_ARTIFACT_TYPES`, `CLAUDE_CODE_REMOTE`\n\n- Flag `tengu_cobalt_plinth_larch`: Off in both readings (read for one account on one subscription tier against v2.1.236; this account: off, anonymous baseline: off, compiled default: off)\n- Flag `tengu_cobalt_plinth_bracken`: Off in both readings (read for one account on one subscription tier against v2.1.236; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Artifacts\n- Names: `type_url`, `CLAUDE_CODE_ARTIFACT_TYPES`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}