[FEATURE] CLI-as-remote-control-client — connect to a remote session from another terminal
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
Remote Control currently supports connecting to a running Claude Code session from claude.ai/code (web) and the Claude mobile app. However, there is no way to connect from another Claude Code CLI instance.
For users who prefer the terminal experience over web/app interfaces, this is a significant gap. The current workaround is SSH + tmux into the host machine, which works but means interacting with the host's terminal session directly rather than through a proper remote control connection.
Proposed Solution
Add a CLI client mode for remote control, e.g.:
claude remote-control --connect <session-id-or-name>This would allow a Claude Code CLI on Machine B to connect to a session running on Machine A — functioning identically to how claude.ai/code and the mobile app connect today, but preserving the full terminal experience (TUI, keyboard shortcuts, tool approval prompts, etc.).
Use Case
- A headless server or always-on machine runs Claude Code with full access to the project filesystem, MCP servers, and local tools
- A laptop or other workstation connects to that session via CLI remote control
- The user gets the terminal-native workflow they prefer, with the compute and filesystem access of the remote machine
- This complements the existing web/mobile clients rather than replacing them — different users prefer different interfaces
How This Differs from Existing Requests
- Not session handoff (#31992) — this is about simultaneous remote interaction with a live session, not moving a session between machines
- Not headless mode (#30447) — though headless mode would complement this feature, they solve different problems. Headless removes the TTY requirement on the host; this adds a CLI client on the connecting side
Priority
Medium - Would be very helpful
Feature Category
CLI commands and flags
Alternative Solutions
- SSH + tmux into the host machine (works, but bypasses the remote control protocol and requires direct SSH access)
- Use claude.ai/code in a browser (works, but loses the terminal-native experience)
Additional Context
_No response_
5 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
IMHO, connecting to remote Claude code session from another CLI or Desktop should be protected with Anthropic account authentication each time if this feature is to be implemented. Unlike the mobile app, which run on personal device, or claude.ai/code, whose authentication can expire with browser session, people don't really log out from CLI or Desktop often, and it could be dangerous if other users are able to access personal remote sessions spawn with your account, especially if you run CLI on a shared server.
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
Would it be possible to reopen this? The closure was auto-triggered by the stale bot, not a product decision. After the possible-duplicate flag, @HungRueiChen's comment engaged constructively with the proposal — raising a worthwhile security consideration around CLI-to-CLI connections that seems sound and would clearly warrant being incorporated into any implementation.
The three issues the bot flagged as possible duplicates address adjacent but distinct problems — session handoff (#31992), headless mode (#30447, #28535) — none propose a CLI client that connects to a live remote session. That distinction is what this request is about.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.