{"version":"2.1.273","anchor":"artifact-template-field-no-longer-gated","canonical_anchor":"artifact-template-field-no-longer-gated","heading":"Artifact template field no longer gated","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/artifact-template-field-no-longer-gated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Artifact template field no longer gated\n\nSetting a template on a new artifact no longer requires a feature flag to take effect\n\n**What**\n\nWhen Claude Code builds the request to create an artifact, the `template` field is now included whenever a template is specified. Previously, including it also required an internal feature check to pass; that check has been removed.\n\n**Why**\n\nArtifact templates now work consistently whenever one is specified, rather than depending on an additional gate.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}