{"version":"2.1.290","anchor":"enterworktree-refuses-switches-that-would-lose-write-access","canonical_anchor":"enterworktree-refuses-switches-that-would-lose-write-access","heading":"Switching into a worktree is refused if it would leave Claude unable to edit","tier":"notice","area":"Worktrees","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/enterworktree-refuses-switches-that-would-lose-write-access","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Switching into a worktree is refused if it would leave Claude unable to edit\n\n`EnterWorktree` now checks first and refuses to switch into an existing worktree where the agent would not have write access\n\n**What**\n\n`EnterWorktree` is the tool that moves a session into a git worktree, an extra working copy of a repository. When entering an existing worktree, it now checks first. If the agent would not get write access there, the switch is not made and an error explains why. Before, the switch went ahead without a check.\n\n**Why**\n\nAn agent no longer ends up in a working copy where it cannot change any files.\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}