{"version":"2.1.275","anchor":"quickstart-flow-now-handles-a-missing-docs-connector-explici","canonical_anchor":"quickstart-flow-now-handles-a-missing-docs-connector-explici","heading":"Quickstart flow now handles a missing Docs connector explicitly","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/quickstart-flow-now-handles-a-missing-docs-connector-explici","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Quickstart flow now handles a missing Docs connector explicitly\n\nArtifact quickstart now explains clearly when no Claude Docs connector is attached\n\n**What**\n\nWhen starting a new artifact of type 'document' without a first-party Claude Docs connector attached to the session, Claude Code now shows a dedicated explanation that a Docs artifact can only be filled in through that connector, and suggests making a plain page instead. The general list of available artifact types also now notes this caveat, and adjusts its \"No published Artifact types\" message to \"No other published Artifact types\" when the Docs connector is the reason.\n\n**Why**\n\nThis makes it clearer why a Docs-type artifact isn't available in a given session, instead of leaving the user to guess why that option is missing.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}