{"version":"2.1.274","anchor":"better-error-messages-when-artifacts-need-a-claudeai-login","canonical_anchor":"better-error-messages-when-artifacts-need-a-claudeai-login","heading":"Better error messages when Artifacts need a claude.ai login, especially in remote\/injected-credential sessions","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/better-error-messages-when-artifacts-need-a-claudeai-login","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Better error messages when Artifacts need a claude.ai login, especially in remote\/injected-credential sessions\n\nError messages for Artifacts requiring a claude.ai login are now more specific about remote and host-injected-credential sessions\n\n**What**\n\nWhen Artifacts (Claude's rendered code\/content outputs) need you to be signed in to claude.ai and you're not, Claude Code now shows a more precise error depending on your situation:\n\n- A generic message telling you to run `\/login`\n\n- A remote-session message explaining that the host machine (the one actually running the session) needs to be signed in\n\n- A message for sessions where credentials are injected by the host environment, noting this can't be changed locally\n\n**Why**\n\nPreviously the login error was likely one generic message regardless of setup. Now, if you're in a remote session or one where your login comes from the environment rather than a local `\/login`, the error tells you where the actual problem is instead of pointing you at a command that won't fix it.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}