You'll notice
Error messages for Artifacts requiring a claude.ai login are now more specific about remote and host-injected-credential sessions
What
When 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:
- A generic message telling you to run
/login - A remote-session message explaining that the host machine (the one actually running the session) needs to be signed in
- A message for sessions where credentials are injected by the host environment, noting this can't be changed locally
Why
Previously 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.
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agree
Improved Claude apps gateway sign-in rate limit errors: /login now explains the refusal, and the gateway log says which limit was hit and…