claude-code - 💡(How to fix) Fix Remote Control: session shows "Connected" on mobile but cannot be selected as remote environment on e ither client [2 comments, 3 participants]

Environment

• Claude Code CLI: 2.1.123
• Claude Code Desktop (Windows): updated to latest as of 2026-04-29
• Claude AI mobile app (iOS): latest, signed in with same Claude Max account
• OS: Windows 10 Pro 22H2 (build 19045)
• Account: Claude Max (OAuth), same on all three clients

Summary

After invoking /remote-control in an active CLI session, the bridge appears to register: a bridgeSessionId is written to ~/.claude/sessions/<pid>.json, and the session shows up as Connected in the Claude AI mobile app's Code tab. However, no client offers a way to actually select the session as a remote environment:

• Claude Code Desktop (Windows): the environment selector lists Local / Cloud / SSH normally, but Remote Control reads "No active sessions." even while mobile shows the same session as Connected.
• Claude AI mobile (iOS): tapping the Connected session opens it as a regular cloud chat — there is no UI affordance to attach it as a remote environment / send commands that execute on the local CLI.

So the bridge handshake half-succeeds (status shows Connected on mobile, bridgeSessionId is issued) but the user-facing "use as remote environment" capability is missing on both clients.

Reproduction

1. Update CLI to 2.1.123 and Desktop to the version released 2026-04-28; ensure mobile app is up to date.
2. Sign all three (CLI, Desktop, mobile) into the same Claude Max account.
3. Fully close Desktop and CLI; reopen both.
4. In a fresh CLI session: /remote-control → output: "Remote Control connecting…"
5. Observe:
   • ~/.claude/sessions/<pid>.json now contains a bridgeSessionId.
   • In mobile Claude AI → Code tab, the session appears under "Today" with a green Connected badge.
   • In Desktop → environment selector → Remote Control: "No active sessions."
   • Tapping the Connected entry on mobile opens a regular chat with no remote-environment controls.

Expected

A clear way to use the Connected CLI session as a remote environment from at least one of the clients (Desktop and/or mobile).

Actual

The session is registered (Connected status visible on mobile, bridgeSessionId persisted on disk) but cannot be selected/attached as a remote environment from either client.

Diagnostic data

• ~/.claude/sessions/<pid>.json contains valid bridgeSessionId (e.g. session_01KzBEe1fytt3qkK2uhrdCRc), status: busy, version: 2.1.123, peerProtocol: 1, kind: interactive, entrypoint: cli.
• Most recent debug log under ~/.claude/debug/ has zero entries matching bridge|remote|register|wss|websocket|handshake|connect.
• ~/.claude/telemetry/ has no failed-events file from this session (the only such file predates this issue by ~6 days).
• No env vars block remote-control eligibility.

Notes

Performed full clean restart of CLI, Desktop, and mobile after updating all three; symptom persists. The split state (mobile shows Connected, Desktop shows No active sessions) is itself probably a clue: the Connected-badge query on mobile sees the registered bridge session that the Desktop selector does not.

Screenshots available on request (Desktop env selector showing "No active sessions" and mobile Code tab showing the same session as Connected).