{"version":"2.1.229","anchor":"custom-artifact-viewer-host-not-yet-resolvable","canonical_anchor":"custom-artifact-viewer-host-not-yet-resolvable","heading":"Custom artifact viewer host, not yet resolvable","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/custom-artifact-viewer-host-not-yet-resolvable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Custom artifact viewer host, not yet resolvable\n\nAn env var for a custom artifact viewer host is recognised but currently ignored.\n\n**What**\n\n`CLAUDE_CODE_ARTIFACT_VIEWER_BASE_URL` is a new recognised environment variable, and artifact URL parsing and building now ask a resolver for the viewer host instead of assuming claude.ai or the staging host. In this build that resolver has an empty body and returns nothing, so the variable is never read and URLs still resolve to the built-in hosts.\n\n**Evidence**\n\n`CLAUDE_CODE_ARTIFACT_VIEWER_BASE_URL`\n\n- Area: Artifacts\n- Names: `CLAUDE_CODE_ARTIFACT_VIEWER_BASE_URL`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}