[FEATURE] CLI-as-remote-control-client — connect to a remote session from another terminal

Resolved 💬 2 comments Opened Apr 27, 2026 by alex-rosenberg35 Closed May 30, 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

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
  • #37345 — closed due to inactivity, but this feature is still highly relevant

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)

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

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