{"version":"2.1.311","anchor":"artifact-prompt-hash-routing-guidance-rewritten","canonical_anchor":"artifact-prompt-hash-routing-guidance-rewritten","heading":"Claude's guidance for links inside artifacts is stricter","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/artifact-prompt-hash-routing-guidance-rewritten","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Claude's guidance for links inside artifacts is stricter\n\nArtifact instructions now limit link anchors to letters, digits and hyphens, warn against secrets in them and reserve `comment-*`\n\n**What**\n\nAn artifact is a self-contained page or small app that Claude builds for you. The instructions Claude follows when building one now say this about the hash, the part of a link after `#`:\n\n- Only a plain `#name` passes from the artifact's link to the page.\n\n- The page should react to the hash changing to decide what to show.\n\n- Names should use ASCII letters, digits and hyphens only. The earlier guidance also allowed `.`, `_` and `~`.\n\n- Keys, tokens and private values must stay out of the hash, because it shows in browser history and in copied links.\n\n- Names starting with `comment-` are reserved.\n\n**Why**\n\nThis changes how artifacts Claude builds handle deep links, meaning links that open straight to one part of the page. Links into artifacts should be simpler and should not leak private values when shared.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}