Source Intelligence

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.242 Home All releases olderv2.1.241 v2.1.243newer
Claude Code v2.1.242

Cloud session event posting returns structured outcomes

Under the hood
Useful2 Signal2
Cloud Sessions

Cloud event posting now distinguishes a dead session from a network failure.

What

Posting an event to a cloud session now returns a named outcome instead of a value or null, so an event sent to a session that is no longer running is distinguished from a network failure.

Details
  • Outcomes: accepted (with a sequence number), session inactive, or failed with a cause separating HTTP, timeout and network errors.
  • An inactive session logs "(session not active)" and increments a remote_send_event_session_inactive counter.
  • Control responses can now supply their own message identifier and are counted as sends.
Evidence

remote_send_event_session_inactive

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

See this entry in the whole of v2.1.242 →