Artifact auth errors now tell you a claude.ai login is needed and to run /logout to clear an API key.
What's wrong with this entry?
When artifact publishing fails because the session is signed in the wrong way, the error now says artifacts need a claude.ai login, and if a Console API key was saved by an earlier /login it tells you to run /logout to clear it.
- Applies to sessions authenticated through a federated environment setup, where the saved credential can be a Console API key rather than a claude.ai account.
- A 404 when loading comment threads on an artifact no longer speculates that the artifact was republished.
- A publish response is now rejected if the returned slug is malformed, not just if fields are missing.
a Console API key saved by a previous /login
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Wrong-account device token now gets its own message
Both mention logout
-
v2.1.222
MCP server panel explains a rejected claude.ai session token
Both mention login
-
v2.1.222
MCP: rejected claude.ai session token is now visible
Both mention login