Release 2.0.78 (2026-06-01)

Bug fixes

• scope session resolve to the current cwd's project slug vrg-vm session <workspace> could hard-fail with "No conversation found with session ID: " — and then refuse to start or resume anything.

The in-VM resolver discovered sessions by globbing every project slug and matched them to a workspace by the path embedded in each session's agent-name, never checking that the transcript physically lives under the slug claude --resume searches (the current cwd's slug). A name-path that points elsewhere than its transcript (from an out-of-band /name rename or running the resolver in a different directory) made the resolver build a slot and exec claude --resume <id> from a cwd where the transcript doesn't exist.

Scope discovery in the resolve path to the current cwd's project slug, the same directory claude --resume reads. list --sessions keeps its full-scan view. This turns the hard failure into the correct fallback: create a fresh session when none is resumable for the workspace.