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.248 Home All releases olderv2.1.247 v2.1.250newer
Claude Code v2.1.248

Resume conflicts say when the session is open interactively

You'll notice
Useful4 Signal3
Sessions

Resume now tells you when the conversation is already open in another running session.

What

If you try to resume a conversation that another process already holds, Claude Code now checks every holder rather than one, prefers an interactive one, and shows a message naming that case: the conversation is already open in another running Claude session, so use that one or close it. Failures also return an explicit resume_session_live_elsewhere code.

Details
  • The conflict telemetry event gained a holder_kind field.
  • Non-interactive holders still get the generic message.
Evidence

This conversation is already open in another running Claude session \u2014 use that one, or close it and try again

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.248 →