{"version":"2.1.242","anchor":"bridge-worktrees-now-use-the-same-storage-backend-as-the-ses","canonical_anchor":"bridge-worktrees-now-use-the-same-storage-backend-as-the-ses","heading":"Bridge worktrees now use the same storage backend as the session","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/bridge-worktrees-now-use-the-same-storage-backend-as-the-ses","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Bridge worktrees now use the same storage backend as the session\n\nRemote session worktrees now store their state in the same place as the session itself.\n\n**What**\n\nWorktree creation and cleanup in remote sessions were made without the session's storage-format setting, so the two could disagree about where state lived. All four call sites now pass it.\n\n**Details**\n\n- Covers creation, normal cleanup, forced cleanup after a failed spawn, and cleanup at shutdown.\n\n**Evidence**\n\n`storageV5: e.storageV5`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}