{"version":"2.1.248","anchor":"resume-resolves-worktree-paths-through-the-storage-layer","canonical_anchor":"resume-resolves-worktree-paths-through-the-storage-layer","heading":"\/resume resolves worktree paths through the storage layer","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/resume-resolves-worktree-paths-through-the-storage-layer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### `\/resume` resolves worktree paths through the storage layer\n\n\/resume now resolves worktree locations through storage, falling back to the recorded path.\n\n**What**\n\nListing resumable sessions now asks the storage backend where a git worktree actually lives, instead of trusting the path recorded when the session was registered. If resolution fails it logs and falls back to the registered path, so `\/resume` still lists the session.\n\n**Details**\n\n- Requires both a feature check and an available storage handle; without either, the old registered-path behaviour applies unchanged.\n- The filter that groups sessions by the same identifier gained an extra argument carrying storage context.\n\n**Evidence**\n\n`\/resume: worktree path not resolved through the storage backend`\n\n- Area: Sessions\n- Names: `\/resume`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}