{"version":"2.1.323","anchor":"enterworktree-honours-blockfiletoolreadsoutsideworkingdirect","canonical_anchor":"enterworktree-honours-blockfiletoolreadsoutsideworkingdirect","heading":"EnterWorktree now stays inside the folders allowed at launch","tier":"notice","area":"Worktrees","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/enterworktree-honours-blockfiletoolreadsoutsideworkingdirect","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### EnterWorktree now stays inside the folders allowed at launch\n\nWith file reads limited to launch folders, EnterWorktree refuses worktrees outside them and moves the session back if a later check fails\n\n**What**\n\nA worktree is a separate working copy of a git repository, which Claude creates and enters with the EnterWorktree tool. When `permissions.blockFileToolReadsOutsideWorkingDirectories` is on, EnterWorktree now checks the target against the folders the session was launched with:\n\n- It refuses to create, enter or move into a worktree outside those folders.\n\n- If a check fails after the move, it returns the session to its previous folder.\n\n- After such a return, the error says where the session now is.\n\nPreviously the only check was the permission prompt asking to enter the worktree.\n\n**Why**\n\nWorktrees could otherwise be used to get around the setting that confines Claude to its launch folders.\n\n- Area: Worktrees\n- Names: `EnterWorktree`, `permissions.blockFileToolReadsOutsideWorkingDirectories`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: yes"}