Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [FEATURE] CLI-as-remote-control-client — connect to a remote session from another terminal [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#53719•Fetched 2026-04-28 06:48:51
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
alex-rosenberg35alex-rosenberg35
Participants
alex-rosenberg35alex-rosenberg35github-actions[bot]github-actions[bot]
Timeline (top)
labeled ×2commented ×1

Fix Action

Fix / Workaround

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.

Code Example

claude remote-control --connect <session-id-or-name>
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • 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

extent analysis

TL;DR

Implement a CLI client mode for remote control to connect to a running Claude Code session from another Claude Code CLI instance.

Guidance

  • Investigate the feasibility of adding a --connect flag to the claude remote-control command to establish a connection to a remote session.
  • Consider the requirements for session identification, such as using a session ID or name, and how to handle authentication and authorization.
  • Evaluate the need for additional flags or options to customize the remote control connection, such as specifying the remote machine's address or port.
  • Review the existing remote control protocol used by the web and mobile clients to ensure compatibility with the proposed CLI client mode.

Example

claude remote-control --connect <session-id-or-name>

This example illustrates the proposed syntax for connecting to a remote session via the CLI.

Notes

The implementation details of the CLI client mode will depend on the specific requirements and constraints of the Claude Code system, including security, authentication, and compatibility with existing features.

Recommendation

Apply workaround: Implement the proposed CLI client mode for remote control to provide a terminal-native experience for users who prefer the terminal interface. This will address the current gap in functionality and provide a more seamless experience for users.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#prompt formatting#chain error#conversation history#tool integration#LLM response

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING