Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.232 Home All releases ←olderv2.1.231 v2.1.233newer→
Claude Code v2.1.232

Artifact commands now require a claude.ai login specifically

You'll notice
Useful4 Signal3
Artifacts

Artifact commands now need a claude.ai login and fail fast if you're on an API key.

/login
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 failed and 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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.232 →