[FEATURE] Feature request: in-session /remote-control toggle to enable Remote Control on an already-running session

Open 💬 5 comments Opened May 19, 2026 by commodore65

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

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_

View original on GitHub ↗

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