{"version":"2.1.311","anchor":"artifact-vs-document-connector-routing-prompt-reworded","canonical_anchor":"artifact-vs-document-connector-routing-prompt-reworded","heading":"Clearer rule for when Claude writes a document or publishes an artifact","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/artifact-vs-document-connector-routing-prompt-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Clearer rule for when Claude writes a document or publishes an artifact\n\nClaude now sends only text people will keep editing, like memos, plans and specs, to the document connector, and makes artifacts for things meant to be viewed or used\n\n**What**\n\nClaude's instructions now draw a different line between writing a document through Anthropic's own document connector (a link to an outside service) and publishing an artifact (a standalone piece of output).\n\n- Documents: only writing people will keep editing or pass around as text, such as a memo, plan, spec, proposal or meeting notes\n\n- Artifacts: anything made to be looked at or used, such as visual or interactive work, or an explainer\n\nBefore, any request for a document or a page of text went to the connector.\n\n**Why**\n\nSome text requests that used to become documents will now come back as artifacts, depending on whether the result is meant to be edited or looked at.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}