[FEATURE] Terminal client for Remote Control sessions — `claude connect <session>` to attach from the CLI like the mobile/desktop apps do
Problem:--remote-control exists only host-side. The only clients that can attach to a Remote Control session are the Claude mobile and desktop apps — there is no CLI counterpart (verified against v2.1.200 --help; claude agents / claude attach only manage the local machine's background sessions).
Use case:
We run an always-on claude remote-control host (systemd service in a container on the home LAN, with that host's credentials and network position). From a phone, attaching is great. But when working from a laptop terminal, there's no way to join that same session: the choices are the desktop app (leaving the terminal) or ssh/tmux into the host machine (requires a direct network path/VPN — which defeats the point, since the Remote Control channel itself is outbound and works from anywhere — and lands you in a different, new session rather than the running one).
Proposed:claude connect [session-name-or-id] —
- no args: list the account's active Remote Control sessions (like the apps do);
- with a target: attach the terminal to that session over the same session infrastructure the apps use (
api.anthropic.com/v1/code/sessions/…), with normal terminal UX: streaming output, permission prompts,/model, detach key.
Prior art in the CLI: --teleport already brings a claude.ai cloud session into the local terminal — this request is the analogous client for Remote Control sessions (attach live, rather than import).
Why terminal instead of the desktop app: tmux/mosh embedding, keyboard-only workflows, machines where the desktop app isn't installed, and consistency — the host side is a CLI feature, so the client side being app-only feels like a gap in the same feature.
Adjacent: #73924 (SessionEnd lifecycle for long-lived remote-control hosts).