[FEATURE] Remote Control session resume is undiscoverable in the CLI

Resolved 💬 5 comments Opened May 5, 2026 by ajogamestudio Closed Jun 2, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Summary

Resuming a previously-active Remote Control (RC) session — so a phone client can reconnect to the existing conversation — is currently undiscoverable. The interactive --resume picker silently hides RC sessions, the working command isn't documented, and the underlying flag is hidden from --help. A user who has had a phone session disconnect (network drop, laptop sleep, server timeout) has no obvious path back to their conversation.

Steps that fail

  1. claude --resume → picker shows local-terminal sessions only. RC sessions are absent with no explanation.
  2. claude --remote-control --resume → same picker as #1. The --remote-control flag does not change which sessions are listed.
  3. claude --help → the --remote-control flag itself is hidden (only --remote-control-session-name-prefix appears), so a user can't even confirm the flag exists from --help.
  4. From the phone client, when the server has died, there's no "reconnect to your last session" affordance — the user has to know to go to their Mac and restart something.

What actually works (undocumented)

claude --remote-control --resume <uuid-of-prior-rc-session>

Where <uuid> has to be hunted manually:
ls -lt ~/.claude/projects/<encoded-project-path>/*.jsonl

…and identified by inspecting the .jsonl contents. There's no in-CLI affordance for finding the right UUID for an RC session.

Proposed Solution

Suggested improvements (any of these would help)

  1. Show RC sessions in --resume pickers, perhaps with an [RC] tag, so the user can pick one without manual UUID lookup. Or add a separate --resume-rc / --resume --remote-control filter that actually filters to RC sessions.
  2. Document --remote-control --resume (or whatever the canonical resume-RC command is) in the Remote Control docs. Today the docs imply RC sessions can't be resumed at all.
  3. Surface --remote-control in claude --help.
  4. Phone-side "reconnect to last session" — when the phone client can't reach the server, offer a clear path that triggers the right command on the paired machine.
  5. At minimum: when claude --resume filters out RC sessions, print a one-line hint like "N Remote Control sessions hidden. Use claude --remote-control --resume <uuid> to resume one."

Environment

  • macOS
  • Claude Code 2.1.128

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

I think this is self-explanatory. My remote-control sessions die all the time and I need an easier way of restarting the correct session.

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗