We should probably mint a new ID to use instead of reusing the original Claude ID. Unclear if our current rehydration will clobber existing session history (probably?), that should be tested further.
Here's some output I got when trying to resume a session that happened to still be running in the background.
cargo run -p path-cli resume https://pathbase.dev/u/user/pathstash/graphs/some_UUID --picker skim
Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.48s
Running `target/debug/path resume 'https://pathbase.dev//u/user/pathstash/graphs/some_UUID' --picker skim`
Resolved https://pathbase.dev//u/user/pathstash/graphs/some_UUID → pathbase-user-pathstash-some_UUID
Picked harness: claude (source)
Resuming: claude -r some_UUID (cwd: /Users/user/project/.claude/worktrees/local-worktree)
Session some_UUID is currently running as a background agent (bg). Use `claude agents` to find and attach to it, or add --fork-session to branch off a copy.
We should probably mint a new ID to use instead of reusing the original Claude ID. Unclear if our current rehydration will clobber existing session history (probably?), that should be tested further.
Here's some output I got when trying to resume a session that happened to still be running in the background.