{"version":"2.1.302","anchor":"background-boot-worktree-adoption-reworked","canonical_anchor":"background-boot-worktree-adoption-reworked","heading":"Background sessions take over a worktree under different conditions","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/background-boot-worktree-adoption-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Background sessions take over a worktree under different conditions\n\nA background session no longer needs a saved worktree path to take over a worktree at startup, but only does so in a matching worktree layout\n\n**What**\n\nA background session is a Claude Code session that runs without being attached to your terminal. A worktree is a separate working copy of a git repository. When a background session starts, it can adopt, or take over, a worktree.\n\nIt previously did nothing if no worktree path had been saved. It no longer needs a saved path. It adopts a worktree only when it starts inside a matching worktree layout, and a further check can stop the adoption.\n\n**Why**\n\nThis changes which background sessions end up working in a worktree when they start.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}