Worktree Symlink Safety Checks / Claude Code v2.1.193

What

Worktree setup now checks that entries in .worktreeinclude and settings.local.json copies do not resolve to destinations outside the worktree via committed symlinks, and skips them if they do.

Details

Logs: "Skipping .worktreeinclude entry: destination escapes worktree via committed symlink: X"
Logs: "Skipping settings.local.json copy: destination escapes worktree via committed symlink"
Prevents a worktree setup from being used to read or write files outside the isolated checkout.

Evidence

New safety messages (search for "destination escapes worktree via committed symlink")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.193 →

The build it came inv2.1.193

25 Jun 2026 · 19 entries, this one is #15.

Either side of it

v2.1.191Older
v2.1.195Newer

Open the release →

Names in this entry

settingsettings.local.json
The runner can warn about or block repo-committed settings that grant access outside the workspace.

Is this right?

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.