{"version":"2.1.314","anchor":"sandbox-rebuilt-when-resuming-into-a-worktree","canonical_anchor":"sandbox-rebuilt-when-resuming-into-a-worktree","heading":"Resuming a session in a worktree now reapplies sandbox protections or stops","tier":"notice","area":"Sandbox","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/sandbox-rebuilt-when-resuming-into-a-worktree","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Resuming a session in a worktree now reapplies sandbox protections or stops\n\nResuming into a worktree now refreshes the sandbox settings, and resume fails with a message suggesting `--fork-session` if that is not possible\n\n**What**\n\nA worktree is a separate working copy of a git repository. A sandbox is a set of limits on what commands Claude runs can reach. Resuming continues an earlier session.\n\nWhen you resume a session into a worktree, Claude Code now refreshes the sandbox settings for it. If it cannot, the resume stops with the error \"could not apply the sandbox's protections to this session's worktree\", and the message suggests running again with `--fork-session`, which starts a new session ID instead of reusing the original.\n\n**Why**\n\nBefore, a resumed worktree could end up running without its sandbox protections. Now it either has them or does not start.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}