What
Every artifact request (list, read, comments, delete, publish) now checks for a claude.ai OAuth token instead of accepting any authenticated session. Setups signed in by API key or other means get Not authenticated — run /login (no claude.ai login) immediately rather than a failed network call.
Details
- The endpoints affected are
/api/frame/frames,/api/frame/read/...,/api/frame/comments/...and the artifact delete and publish paths. - The check returns
{ ok: !1, reason: "no-auth", detail: "no claude.ai login" }before any request is sent. - The token refresh that runs before each call moved into a helper that logs
firstPartyApi: refreshOAuth failedand continues with the cached token instead of failing the whole call.
Evidence
no claude.ai login
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle/login
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…