A parked agent refuses to resume if its worktree disappeared, instead of landing in the wrong directory.
What's wrong with this entry?
Resuming a parked or isolated agent verifies the recorded worktree first and refuses rather than silently landing somewhere else.
- stats and verifies the recorded worktree and touches it
- falls back to a covered directory only when the session's fences cover it
- otherwise raises a terminal error saying the agent cannot be resumed
This agent cannot be resumed: its worktree
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.
-
v2.1.239
worktree.locationsetting for Desktop SSH sessionsBoth mention worktree
-
v2.1.246
Worktree cleanup only removes directories Claude Code created
Both mention worktree
-
v2.1.247
Cloud-session seeding names linked worktrees and split git layouts as un-seedable
Both mention worktree