{"version":"2.1.287","anchor":"exitworktree-rehomes-background-session-state","canonical_anchor":"exitworktree-rehomes-background-session-state","heading":"Leaving a worktree now also moves background session state to your folder","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/exitworktree-rehomes-background-session-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Leaving a worktree now also moves background session state to your folder\n\nWhen ExitWorktree returns you to your original folder, it now moves the saved state of background sessions there too\n\n**What**\n\nA worktree is a separate copy of your project checked out in its own folder, and ExitWorktree is the tool Claude uses to leave one. When it takes you back to your folder, it now also moves the saved state for background sessions to that folder. A background session is a Claude Code session that keeps working while you do something else.\n\nIf moving that state fails, Claude Code records the failure and carries on leaving the worktree instead of stopping.\n\n**Why**\n\nBackground sessions now follow you out of the worktree instead of staying tied to the folder you left. A problem moving them does not block you from getting back to your project.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}