{"version":"2.1.287","anchor":"artifacts-create-runner-strict-relay-and-clearer-error","canonical_anchor":"artifacts-create-runner-strict-relay-and-clearer-error","heading":"Creating an artifact in some sessions gives a clearer error when Artifacts is unreachable","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/artifacts-create-runner-strict-relay-and-clearer-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Creating an artifact in some sessions gives a clearer error when Artifacts is unreachable\n\nIn some sessions, failing to create an artifact now says the session could not reach Artifacts instead of telling you to run `\/login`\n\n**Unclear.** It is not clear exactly which sessions get the new message.\n\n**What**\n\nWhen creating an artifact fails because Claude Code has no way to authenticate, some sessions now show \"This session could not reach Artifacts: ...\" instead of \"Not authenticated, run `\/login`\". When Claude Code runs as a runner, creating an artifact also goes through a stricter relay route.\n\n**Why**\n\nIn hosted sessions, telling you to run `\/login` was not useful advice, so the new message describes the actual problem.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}