Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.232 ·

One consistent message when artifact commands need you to log in

Publishing and listing artifacts now share one "Not authenticated, run /login" message.

You'll notice Improvements
JSON All of v2.1.232
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.232,
ImprovementsSection of the release
What

Publishing an artifact and listing artifacts now report authentication failures with the same wording, which starts with "Not authenticated", tells you to run /login, and puts the underlying detail in parentheses. The older separate phrasings for each command are gone.

Details
  • Failures that are not about authentication still read "publish unavailable: " and "artifact listing unavailable: " with the detail appended.
Evidence

artifact listing unavailable:

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundle/login
Since it was published

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 block changelog see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up /login, on Claude Code changelog.
Anthropic's release notes agreeFixed Cloud gateway /login exiting silently or leaving an unresponsive terminal after "Press Enter to continue" when managed settings failed…

See this entry in the whole of v2.1.232 →

Feedback