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

Worker disconnects say which conflict happened

You'll notice
Useful2 Signal2
Cloud Sessions

Cloud worker rejections now name the specific conflict: archived, superseded or stale epoch.

What

When a cloud worker connection is rejected as conflicting, the reason is now more specific: a session that is archived or no longer active, or one superseded by a newer worker, are reported separately from a stale epoch.

Details
  • superseded_by_worker and session_not_active join epoch_stale and epoch_conflict, all closing with code 4090.
  • Diagnostics read "session archived or no longer active" and "superseded by a newer worker".
  • The session-not-active case emits its own telemetry event.
Evidence

cli_worker_session_not_active

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 →