Restarting `claude rc` cannot continue a session that was cut off in the mobile app
Follow-up to #68606, which the stale bot closed with "open a new issue if this is still relevant."
What happened
I was driving claude rc on my own machine from the Claude mobile app. The machine died mid-session. After it came back I ran claude rc in the same repository and reconnected from the app — and there was no way to continue the session I had been working in. A fresh session was created instead. The mobile app offered nothing to reattach to.
The work was not lost — the transcripts were on disk the whole time — but nothing in the CLI or the app leads you to them.
Why the existing ask does not cover this
#68606 asks for the session list to rehydrate from on-disk transcripts for the server's cwd. That would not have helped: the sessions were never filed under the server's cwd.
claude rc spawns each session into <repo>/.claude/worktrees/bridge-cse_<session-id>/, and that worktree path becomes the session's project key:
~/.claude/projects/<repo>/ ← the server's cwd
~/.claude/projects/<repo>--claude-worktrees-bridge-cse-…/ ← where the transcript is
Nothing in the cwd's project directory points at them — bridge-pointer.json names only the newly created session. There is no mapping on disk, in either direction, between the repository I ran claude rc in and the sessions it spawned.
Repro
claude rcin a git repository; start a session from the mobile app and do some work.- Kill the host or the
claude rcprocess. - Restart and run
claude rcin the same repository; reconnect from the app.
The interrupted session cannot be continued from either side, and a fresh one is created.
Ask
Restarting claude rc should offer the sessions it previously spawned for that directory. Extending #68606's fix to cover <dir>/.claude/worktrees/*, or having the spawning directory record where it put the session, would do it.
Environment
Claude Code 2.1.232, Linux (WSL2), claude rc server mode driven from the mobile app.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗