remote.enableRemoteControlForAllSessions does not auto-connect sessions for remote control
Resolved 💬 2 comments Opened Apr 8, 2026 by lda21 Closed May 21, 2026
Bug Description
The setting remote.enableRemoteControlForAllSessions: true in settings.json does not automatically make sessions visible in the Claude app (mobile/web) for remote control.
Steps to Reproduce
- Add the following to
~/.claude/settings.json:
``json``
"remote": {
"enableRemoteControlForAllSessions": true
}
- Start a new Claude Code session
- Open the Claude app (mobile or web) and look for the session
Expected Behavior
The session should automatically appear in the Claude app for remote control, without any additional steps.
Actual Behavior
The session does not appear in the Claude app. It only becomes visible after manually running /remote-control inside the session.
Environment
- Claude Code version: 2.1.96
- OS: Linux (Ubuntu)
- Auth: OAuth (Claude Max subscription)
Notes
- There is no CLI flag (e.g.
--remote-control) to auto-enable this at session start either - The setting name strongly implies it should enable remote control automatically for all sessions
- Workaround: manually run
/remote-controlin each session
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗