claude-code - 💡(How to fix) Fix [FEATURE] Feature request: in-session /remote-control toggle to enable Remote Control on an already-running session [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#60699Fetched 2026-05-20 03:51:48
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1
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

Summary

Currently, Remote Control can only be enabled at session start, via the --remote-control CLI flag. There is no way to toggle it on (or off) inside a running session.

Use case

I frequently want to attach my phone to a session that is already in flight — long-running task, full context, lots of files read, partial plans on screen. Today the only path is:

  1. Exit the session
  2. claude --resume <id> --remote-control
  3. Pick the session from the picker, wait for it to rehydrate

This works but is heavy for what is essentially a connectivity toggle, and it forces a context reload every time I want to step away from the desk.

Proposal

Bring back (or add) an in-session slash command:

  • /remote-control — enable RC on the current session, print/show the QR + URL
  • /remote-control off — disable RC and invalidate the pairing
  • /remote-control status — show whether RC is active, current session name, connected device(s)

Same auth/permission model as the CLI flag — no new surface area, just a runtime toggle.

Why it matters

  • Mobility without losing context (the whole point of RC for many of us)
  • Symmetry with other session features that are already toggleable mid-session (e.g. model, effort, plan mode)
  • Lower friction = more people will actually use the mobile app

Environment

  • Claude Code v2.1.145
  • macOS (darwin 25.5.0)
  • Plan: Max (claude.ai OAuth)

Proposed Solution

Bring back (or add) an in-session slash command:

  • /remote-control — enable RC on the current session, print/show the QR + URL
  • /remote-control off — disable RC and invalidate the pairing
  • /remote-control status — show whether RC is active, current session name, connected device(s)

Same auth/permission model as the CLI flag — no new surface area, just a runtime toggle.

Why it matters

  • Mobility without losing context (the whole point of RC for many of us)
  • Symmetry with other session features that are already toggleable mid-session (e.g. model, effort, plan mode)
  • Lower friction = more people will actually use the mobile app

Environment

  • Claude Code v2.1.145
  • macOS (darwin 25.5.0)
  • Plan: Max (claude.ai OAuth)

Alternative Solutions

No response

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

No response

Additional Context

No response

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [FEATURE] Feature request: in-session /remote-control toggle to enable Remote Control on an already-running session [1 comments, 2 participants]