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

/resume resolves worktree paths through the storage layer

You'll notice
Useful3 Signal2
Sessions

/resume now resolves worktree locations through storage, falling back to the recorded path.

/resume
What

Listing resumable sessions now asks the storage backend where a git worktree actually lives, instead of trusting the path recorded when the session was registered. If resolution fails it logs and falls back to the registered path, so /resume still lists the session.

Details
  • Requires both a feature check and an available storage handle; without either, the old registered-path behaviour applies unchanged.
  • The filter that groups sessions by the same identifier gained an extra argument carrying storage context.
Evidence

/resume: worktree path not resolved through the storage backend

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