Isolation refusal messages now say whether the session or the agent is the one confined.
What's wrong with this entry?
The refusals you get when a shell cwd or file edit escapes a worktree now name the right subject.
- picks between "This session is isolated…" and "This agent is isolated…" based on whether the pin is the session's own worktree, with a matching possessive
- shell cwd and file edit paths now share one escape-detection routine
possessive: "a worktree-isolated agent's"
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