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.
Names in the bundle/resume
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Environment variables touched a line naming /resume after this was published.
| `CLAUDE_CODE_SESSIONEND_HOOKS_TIMEOUT_MS` | Override the time budget in milliseconds for [SessionEnd](/docs/en/hooks#sessionend) hooks. The value is also the timeout for each hook that sets no `timeout` of its own. Applies to session exi…env-vars see the edit
Confirmed since
Anthropic's documentation has since written up /resume, on Claude Code changelog.
* Fixed `/resume` listing a `/fork` background session under its parent's name instead of its own `⑂` fork namechangelog see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /resume, on Claude Code changelog.