What
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.
Details
- 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.
Evidence
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.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up /login, on Claude Code changelog.
* Added the `gatewayInternalNetworks` managed setting, letting administrators allow `/login` to a Claude apps gateway on their organization's own public IPv4 blockchangelog see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /login, on Claude Code changelog.
Anthropic's release notes agree
Fixed Cloud gateway /login exiting silently or leaving an unresponsive terminal after "Press Enter to continue" when managed settings failed…