{"version":"2.1.277","anchor":"claudeai-artifact-links-explicit-tool-routing-guidance-add","canonical_anchor":"claudeai-artifact-links-explicit-tool-routing-guidance-add","heading":"claude.ai artifact links: explicit tool-routing guidance added","tier":"internal","area":"Artifact Publish","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/claudeai-artifact-links-explicit-tool-routing-guidance-add","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### claude.ai artifact links: explicit tool-routing guidance added\n\nClaude is now told to read claude.ai artifact links with the Artifact tool or WebFetch, never curl or a headless browser\n\n**What**\n\nClaude Code's instructions now explain that claude.ai artifact links \u2014 of the form `claude.ai\/artifact\/{id}` or `claude.ai\/code\/artifact\/{uuid}`, including on `preview.claude.ai` \u2014 are published artifacts and should be read using the `Artifact` tool's \"read\" action, or via `WebFetch` using the user's claude.ai login. The instructions explicitly warn against fetching such links with `curl` or a headless browser, which return either the app's empty page shell or a Cloudflare 403 error.\n\n**Why**\n\nThis steers Claude toward methods that can actually retrieve artifact content and away from methods that reliably fail on these links, avoiding wasted attempts and confusing error pages.\n\n- Area: Artifact Publish\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}