Skip to content

Add --remote-control CLI flag to enable remote control at session start #39347

Description

@BigfootAU

Summary

There is currently no way to start a Claude Code session with remote control enabled from the CLI. The only options are:

  1. /remote-control slash command inside a running session (requires interactive input)
  2. /config → "Enable Remote Control for all sessions" toggle (affected by bug "Enable Remote Control for all sessions" resets to false despite persisted config #29929 where it resets to false)

Use Case

When managing multiple Claude Code sessions from a mobile device (iPhone via claude.ai/code), the workflow is:

  1. Connect to Session A via remote control
  2. From Session A, spawn a new Terminal tab with a new Claude session
  3. Connect to the new session via remote control

This workflow is currently impossible because the spawned session cannot have remote control enabled programmatically. You must have physical access to the Mac to type /remote-control in the new session.

Requested Feature

Add a --remote-control CLI flag:

claude --remote-control

This would start the session with remote control already enabled, printing the connection URL to stdout immediately. This allows:

  • Spawning remote-controllable sessions from scripts
  • Spawning remote-controllable sessions from other remote-controlled sessions
  • Fully remote management of multiple parallel Claude sessions

Workarounds Attempted

Related Issues

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    duplicateThis issue or pull request already exists

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions