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

Status Fixed / completed
Maintainer reply None cached
Activity 7 comments · opened May 19, 2026 · closed Aug 17, 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

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 ↗

5 Comments

github-actions[bot] · 3 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/29265
  2. https://github.com/anthropics/claude-code/issues/34350
  3. https://github.com/anthropics/claude-code/issues/37589

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

Snailflyer · 3 months ago

This request matches the part of Remote Control that matters most to long-running work: attaching after the session already has context, tool state, and partial work on screen. Having to exit and resume is a heavy workaround because the user is not asking for a new session; they are asking for a control surface for the current one.

I built Faryo around a narrower version of this idea: keep Claude Code/Codex/shell running inside tmux as the durable live session, and let phone/browser attach as a thin workbench for compact output, short input, approval/interrupt, and handoff. It does not fix /remote-control itself, but it is useful when the actual need is "attach to the existing local tmux-backed CLI session without restarting it": https://github.com/Snailflyer/faryo

cdwf01-code · 2 months ago

A toggle would surely be the simplest solution

syjust · 1 month ago

+1 on this. Opened #76071 requesting a dedicated keybinding action (e.g. chat:toggleRemoteControl) for this — closing it as a duplicate in favor of this issue.

A keybinding would make the toggle even more seamless: today actions like chat:fastMode, chat:thinkingToggle, and chat:workflowKeywordToggle are all bindable in ~/.claude/keybindings.json, so remote control should follow the same pattern once the in-session toggle exists.

ljharb · 1 month ago

This is also pretty annoying because when DO_NOT_TRACK is set, remote control doesn't work - and i keep it set so that gh doesn't send telemetry back. If I forget to DO_NOT_TRACK= before claude, then i can't use RC.

Showing cached comments. Read the full discussion on GitHub ↗