{"version":"2.1.319","anchor":"exitworktree-refuses-to-remove-a-worktree-holding-connector","canonical_anchor":"exitworktree-refuses-to-remove-a-worktree-holding-connector","heading":"Leaving a worktree no longer deletes files saved from connectors without asking","tier":"notice","area":"Worktrees","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/exitworktree-refuses-to-remove-a-worktree-holding-connector","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Leaving a worktree no longer deletes files saved from connectors without asking\n\nExitWorktree now refuses to remove a worktree holding files saved from connectors, unless `discard_changes` is set to true\n\n**What**\n\nA worktree is a separate working copy of your project that Claude Code can work in alongside your main one. ExitWorktree is the tool Claude uses to leave a worktree, and it can remove the worktree on the way out. When asked to remove it, ExitWorktree now also checks the worktree's folder of files saved from connectors (outside services Claude Code is linked to).\n\n- If that folder holds saved files, removal is refused unless `discard_changes` is true\n\n- If the folder cannot be checked, removal is also refused unless `discard_changes` is true\n\n- The refusal message lists the saved files alongside any uncommitted files and commits\n\n- A second check right at removal time stops with an error if the folder gained files or could not be read\n\nWhen removal is refused, the session stays in the worktree. Before, only uncommitted files and commits could block removal.\n\n**Why**\n\nFiles saved from connectors are no longer lost without warning when a worktree is removed.\n\n- Area: Worktrees\n- Names: `ExitWorktree`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}