{"version":"2.1.246","anchor":"softer-fallback-when-no-artifact-types-are-published","canonical_anchor":"softer-fallback-when-no-artifact-types-are-published","heading":"Softer fallback when no artifact types are published","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/softer-fallback-when-no-artifact-types-are-published","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Softer fallback when no artifact types are published\n\nWith no artifact types published, Claude just builds what you asked for as normal.\n\n**What**\n\nWhen the list of artifact types is empty or unavailable, the model is told to make the thing the way it otherwise would, and only if the user actually asked for something, replacing the previous instruction to build the artifact itself as usual.\n\n**Details**\n\n- Prompt text only; no behaviour outside what the model reads.\n\n**Evidence**\n\n`If the user wanted something made, make it the way you otherwise would.`\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}