Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix remote.enableRemoteControlForAllSessions does not auto-connect sessions for remote control [1 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#45044•Fetched 2026-04-09 08:14:36
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
lda21lda21
Participants
lda21lda21
Timeline (top)
labeled ×4

Fix Action

Fix / Workaround

  • 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-control in each session

Code Example

"remote": {
     "enableRemoteControlForAllSessions": true
   }
RAW_BUFFERClick to expand / collapse

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

  1. Add the following to ~/.claude/settings.json: 
    "remote": {
  "enableRemoteControlForAllSessions": true
}
  2. Start a new Claude Code session
  3. 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-control in each session

extent analysis

TL;DR

The issue can be worked around by manually running the /remote-control command in each session until the remote.enableRemoteControlForAllSessions setting is properly implemented.

Guidance

  • Verify that the settings.json file is correctly formatted and located in the ~/.claude/ directory.
  • Check if there are any other settings or configurations that might be overriding the remote.enableRemoteControlForAllSessions setting.
  • Consider filing a feature request or bug report to the Claude development team to properly implement the automatic remote control feature.
  • In the meantime, use the workaround of running /remote-control in each session to enable remote control.

Example

No code snippet is necessary for this issue, as it appears to be a configuration or implementation problem.

Notes

The provided information suggests that the issue is likely due to a missing implementation or bug in the Claude Code application, rather than a user configuration error. The workaround provides a temporary solution, but a proper fix would require changes to the application itself.

Recommendation

Apply workaround: Manually run /remote-control in each session, as this is the only known way to enable remote control until the remote.enableRemoteControlForAllSessions setting is properly implemented.

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…
#task chaining#parallel task#integration issue#index setup#retrieval issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING