You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched existing requests and this feature hasn't been requested yet
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
claude --resume → picker shows local-terminal sessions only. RC sessions are absent with no explanation.
claude --remote-control --resume → same picker as Create SECURITY.md #1. The --remote-control flag does not change which sessions are listed.
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.
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
Where <uuid> has to be hunted manually:
ls -lt ~/.claude/projects//*.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)
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.
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.
Surface --remote-control in claude --help.
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.
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.
Preflight Checklist
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
--resumepicker 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
claude --resume→ picker shows local-terminal sessions only. RC sessions are absent with no explanation.claude --remote-control --resume→ same picker as Create SECURITY.md #1. The--remote-controlflag does not change which sessions are listed.claude --help→ the--remote-controlflag itself is hidden (only--remote-control-session-name-prefixappears), so a user can't even confirm the flag exists from--help.What actually works (undocumented)
claude --remote-control --resume
Where
<uuid>has to be hunted manually:ls -lt ~/.claude/projects//*.jsonl
…and identified by inspecting the
.jsonlcontents. There's no in-CLI affordance for finding the right UUID for an RC session.Proposed Solution
Suggested improvements (any of these would help)
--resumepickers, perhaps with an[RC]tag, so the user can pick one without manual UUID lookup. Or add a separate--resume-rc/--resume --remote-controlfilter that actually filters to RC sessions.--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.--remote-controlinclaude --help.claude --resumefilters out RC sessions, print a one-line hint like "N Remote Control sessions hidden. Useclaude --remote-control --resume <uuid>to resume one."Environment
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.