Some internal endpoints now demand a claude.ai login specifically and fail with their own message.
What's wrong with this entry?
Internal endpoints that previously declared their auth requirement as "required" now declare claude-ai-oauth, and the request layer gained a branch that checks for a claude.ai login in particular, fails with its own detail string when there is none, and adds an anthropic-beta header. The old generic value no longer appears anywhere.
- Affected call sites include the artifacts and frame endpoints and artifact unsubscribe.
detail: "no claude.ai 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
Signing back into the same account keeps a pending auto-resume
Both mention auth
-
v2.1.234
Token screen reports actual remaining validity
Both mention auth
-
v2.1.234
Setup-token login result carries the expiry
Both mention auth