{"version":"2.1.281","anchor":"artifact-telemetry-reports-inherited-type-grant-when-the-swi","canonical_anchor":"artifact-telemetry-reports-inherited-type-grant-when-the-swi","heading":"Artifact tool gains gated inherited type capabilities and prompt text variants","tier":"soon","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/artifact-telemetry-reports-inherited-type-grant-when-the-swi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Artifact tool gains gated inherited type capabilities and prompt text variants\n\nTwo new Artifact tool experiments: capabilities inherited from Anthropic-published types, and v0\/v1\/v2 variants of the tool's guidance text\n\n**Unclear.** The finding does not say what an inherited type grant changes about artifact permissions.\n\n**What**\n\nThe Artifact tool, which Claude uses to publish pages, gained two experiments. Both are controlled by server-side gates (switches Anthropic can flip remotely) or by environment variables. Nothing has been read about any of these gates.\n\nInherited capabilities from a type:\n\n- The publish description can append \" [capabilities: declared by the Anthropic-published type this Artifact was made from; this publish cannot change them]\". While that note is shown, the usual connector-grant note is left out.\n\n- The note appears only for a type-locked Artifact with no explicit capabilities or contract, and only when the setting `CLAUDE_CODE_ARTIFACT_INHERITED_TYPE_GRANT` is on or, failing that, the gate `tengu_swirling_squid`, which falls back to false. The result is fixed once per session.\n\n- A schema that already has `watch_rail`, `auto_react` and `db_str_replace` gains an optional `inherited_type_grant` field, and the Artifact configuration report includes `inherited_type_grant: true` when the feature is on. New report fields `type_first_party` and `caps_read_not_found` follow the same switch.\n\nText variants:\n\n- The tool's guidance is now assembled from a table of variants, v0, v1 and v2, covering the head, deliverable, capabilities, storage, update, unread-files and never-publish sections. A variant can reorder them, for example putting capabilities last.\n\n- v1 and v2 carry rewritten text, such as \"Always author the page as `.html`\", a browser-storage section and new rules about updating and reading before publishing.\n\n- The variant is chosen once per session: `CLAUDE_CODE_ARTIFACT_TEXT_VARIANT` first; otherwise v0 when `CLAUDE_CODE_SESSION_ORIGIN` is `claude_ai_chat`; otherwise the gate `tengu_cobalt_plinth_sloe`, which falls back to \"v0\". The interactive tool now builds its prompt with this `textVariant`.\n\n**Why**\n\nThe first experiment would let Artifacts made from an Anthropic-published type take their capabilities from that type, so a publish cannot change them. The second is a test of different wordings of the tool's instructions. The fallback for both is the existing behaviour, and the rendered prompts did not change.\n\n- Flag `tengu_swirling_squid`: Not enough to say (read for one account on one subscription tier against v2.1.281; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 4\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}