{"version":"2.1.274","anchor":"artifact-auto-open-guidance-now-excludes-connector-backed-ty","canonical_anchor":"artifacts-flow-now-routes-documents-to-a-first-party-docs-co","heading":"Artifacts can route documents to a Claude Docs connector, with auto_open adjusted accordingly","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/artifact-auto-open-guidance-now-excludes-connector-backed-ty","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Artifacts can route documents to a Claude Docs connector, with auto_open adjusted accordingly\n\nArtifacts now hand document creation off to a connected Claude Docs connector when available, and auto_open guidance was updated to match\n\n**What**\n\n- When a first-party connector for reading and writing documents (Claude Docs) is attached, the artifacts flow now routes document creation to that connector or its skill instead of creating an Artifact, falling back to the normal quickstart flow otherwise.\n\n- A validation rule that used to block the `auto_open: \"after_first_write\"` option under a certain tool-availability condition has been removed from artifact publishing.\n\n- The instructions Claude sees when starting a new Artifact now explicitly say `auto_open: \"after_first_write\"` should never be used for a type whose content is written through a connector, such as a Claude Docs document.\n\n- The description of the `auto_open` parameter on the artifact-creation tool was simplified, dropping an extra sentence that used to appear only when a certain feature flag was on.\n\n**Why** This avoids opening an artifact automatically for content that is actually being created through a connector like Claude Docs, keeping the auto-open behavior consistent with where the content is really going.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}