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

Resuming with an unrecognisable session id now forks instead of resuming

You'll notice
Useful3 Signal2
Sessions

An unparseable --resume session id now forks and replays instead of quietly resuming.

--resume
What

The session id given by --resume or by the launch config is validated before use. A valid id resumes as before; a non-empty id that does not parse now takes the fork and replay path rather than silently resuming. v2.1.231 resumed on any non-empty id.

Details
  • Accepted forms are a plain UUID, or a prefixed identifier matching ^[A-Za-z0-9][A-Za-z0-9_]*$ whose trailing 01-prefixed base58 segment decodes to a 32-hex-digit UUID.
Evidence

/^[A-Za-z0-9][A-Za-z0-9_]*$/.test(e)

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 →