Remote Control: session not connecting from mobile app

I second this. I am able to get it to work very intermittently. The first time I got it to work I logged out of the cli and back in. I coded for a few hours but then the app suddenly "refreshed" and the session disappeared. I could not get it back. I got it to work on safari but I had to log out and log back in as well.

Experiencing a similar issue.

• Claude Code version: 2.1.59
• OS: Linux (Remote server via SSH)
• Phone: iPhone 12 Pro Max, Claude iOS app (latest)
• Plan: Max

Scanning the QR code from claude remote-control opens the Claude app
but shows the regular chat interface — not the Code/sessions view.
The remote session is not visible.

However, if I open claude.ai/code in Safari and then tap "Open in app",
the Code section loads correctly and I can see my sessions.
So the issue seems to be that the QR code deep link routes to regular
chat instead of the Code section of the app.

Remote Control session starts successfully in the CLI terminal and is accessible from the web browser and the desktop app, but the iOS mobile app does not connect to the session and does not display it in the sessions list. The app only shows the Code onboarding screen with a "Connect to GitHub" button — there is no option to join an existing Remote Control session.

iOS device: iPhone, iOS app version 1.260223.2 (latest, no updates available)
Desktop app: Working correctly — shows Remote Control session
Web browser: Working correctly — shows Remote Control session

QR code scan opens claude app - but opens a chat window not the remote session

Seems like the "Connect to GitHub" screen is gating the page with the list of active remote sessions; i.e.: if you connect github than you'll see your active remote sessions

Seems like the "Connect to GitHub" screen is gating the page with the list of active remote sessions; i.e.: if you connect github than you'll see your active remote sessions

thanks that was actually the issue - even though i haven't conneccted github in web or the windows app either
after connecting github the remote session does display

Facing the same issue. Max plan, macOS (Darwin 23.3.0), Claude Code CLI via npm-global install.

claude remote-control starts successfully and generates a link/QR code. When I open the link on my phone, it opens a normal claude.ai web chat thread instead of connecting to my local CLI session. No error — just a completely disconnected regular conversation.

Facing the same issue. Max plan, macOS (Darwin 23.3.0), Claude Code CLI via npm-global install. claude remote-control starts successfully and generates a link/QR code. When I open the link on my phone, it opens a normal claude.ai web chat thread instead of connecting to my local CLI session. No error — just a completely disconnected regular conversation.

check if your claude code is linked to github on the phone or not, i had same issue but once i got rid of the 'connect to github' message then the remote sessions appeared

The Remote Control onboarding experience on the Claude iOS app is seriously broken. After scanning the QR code from claude remote-control, the app opens but the session simply doesn't appear anywhere. No error message, no prompt, no indication of what went wrong — just nothing.

If it weren't for Claude itself helping me find this GitHub issue thread, I would have had absolutely no idea how to resolve this. The fact that your own AI had to dig through community discussions to figure out a workaround for your own product's UX gap really says something about how undiscoverable this problem is.

tried the github connection fix, didn't work for me. still just opens the app and nothing happens

Still broken in v2.1.75 (Mar 13, 2026).

New behavior observed in v2.1.75:

• Scanning QR code with Claude mobile app: app opens, nothing connects (same as all prior versions)
• Scanning QR code with device camera: opens App Store listing for the Claude app, then opens the existing installed app — but no connection is established. The QR code appears to encode an App Store deep link rather than a session handshake URL, meaning the camera path is a dead end.

Version history for this bug:

• v2.1.58: First confirmed (original report)
• v2.1.70: Poll rate cut 300x (performance fix) — connection still broken
• v2.1.71: Still broken
• v2.1.72: Still broken
• v2.1.73: Still broken
• v2.1.74: Still broken
• v2.1.75: Still broken

This feature has been non-functional across at least 5 consecutive versions. No workaround exists — neither QR scan (mobile app), camera scan (App Store redirect), nor session URL (redirects to claude.ai/code/family) establishes a connection.

Environment: Windows, Node.js install (npm), Max plan, same account on host and mobile device.

Tried both workarounds mentioned in comments (GitHub connect-first, Safari claude.ai/code open-in-app) — neither works. Still fully blocked on v2.1.75. No mobile connection path functional.

v2.1.76 Remote Control fixes — requesting confirmation on mobile QR pairing

v2.1.76 includes what appear to be directly relevant Remote Control server-side fixes:

1. "Fixed Remote Control: sessions silently dying when the server reaps an idle environment" — This is my top candidate for the root cause. When I scan the QR code on mobile, no session appears in the app. If the server was silently killing the session during the mobile handshake window, this would explain the complete silence on both ends.

1. "Fixed bridge sessions failing to recover after extended WebSocket disconnects" — Addresses the no-error-no-connection behavior on mobile.

1. "Fixed stale work items causing redelivery after JWT refresh" — Relevant if the mobile auth token refresh during pairing caused the session to go stale.

My setup for context:

• Host: Windows, Node.js npm install of Claude Code
• Mobile: Claude app, same account (Max plan)
• Behavior: claude remote-control starts fine on host (shows QR + session URL + Waiting for connections). Scanning QR with Claude mobile app — app opens, nothing connects, no green dot. Camera scan opens App Store then the already-installed app, no connection. Session URL on mobile browser redirects to claude.ai/code/family. Broken across v2.1.71 through v2.1.75 (at least 4 consecutive versions with zero Anthropic staff response).

Will update to v2.1.76 and retest. Will report back whether the session-silently-dying fix resolves mobile QR pairing. If anyone else has tested v2.1.76 mobile remote control, please share results here.

Upgraded to v2.1.76 and tested immediately. Mobile QR pairing still broken. The Remote Control server-side fixes (silent session death, bridge recovery, stale work items) did not resolve the mobile connection issue. Now confirmed broken across v2.1.71 → v2.1.76, 6 consecutive versions. Still no workaround.

Same issue here - additional data points:
Environment:
∙ macOS, Mac (jack-mac-2.local)
∙ Claude Code: latest
∙ iOS app: latest (March 2026)
∙ Plan: Max
What works:
∙ claude rc starts successfully, session URL generated
∙ Chrome desktop: connects fine
∙ Chrome iOS: connects fine
∙ Safari desktop (claude.ai/code): connects fine
What doesn’t work:
∙ iOS native app: Session doesn’t appear in Code tab session list. When opened via URL, shows “Unknown network error” and stays stuck on “Connecting”
∙ Safari iOS: Shows “Failed to load session” error page
Notes:
∙ The native iOS app used to work with Remote Control previously
∙ This appears to be a WebKit-specific issue since Chrome (Blink engine) works on both desktop and iOS, while Safari and the native app (which uses WebKit) both fail
∙ Restarting the iOS app, force-quitting, and creating new RC sessions did not help

Additional data point for the WebKit diagnosis above: Windows host, iPhone (iOS), same failure.

• claude remote-control starts on Windows (Node.js npm, v2.1.76, Max plan)
• QR scan with Claude iOS app: app opens, no session appears, no connection
• Same account on both devices, same network
• Chrome iOS workaround not viable for a tool meant to control a CLI session from your phone

So the WebKit failure isn't macOS-specific on the host side — it reproduces with Windows host + iPhone client. The common denominator is the iOS Claude app (WebKit), not anything about the host OS.

@antrewmorrison — confirming this is reproducible on Windows host as well, not just macOS.

v2.1.79 adds /remote-control for VSCode only — "bridge your session to claude.ai/code to continue from a browser or phone." This is exactly the feature we need, but it's not available in the CLI.

For those of us using claude in terminal (not VSCode), claude remote-control is now confirmed broken across v2.1.71 → v2.1.79, 9 consecutive versions. The VSCode implementation working suggests the server-side infrastructure is functional — the CLI's QR pairing path is the remaining gap.

@antrewmorrison — is the VSCode /remote-control bridge using the same session infrastructure as CLI claude remote-control? If so, is there a timeline for bringing parity to the CLI path? Windows host + iPhone (WebKit) still can't connect via any path.

Remote Control mobile still broken on v2.1.79 (CLI)

Environment:

• Version: v2.1.79 (confirmed via claude --version)
• Host: Windows
• Client: iPhone (iOS), Claude mobile app

Failure modes (both still present):

1. Scanning QR code with Claude mobile app — app opens, nothing connects, no green dot appears
2. Scanning QR code with device camera — opens App Store, then Claude app, still no connection established

Note: v2.1.79 added VSCode /remote-control support, but CLI claude remote-control is still broken. Since the VSCode implementation works, the server-side infrastructure is clearly functional — the remaining gap appears to be isolated to the CLI QR pairing path.

@antrewmorrison — any update on CLI parity timeline for this?

Adding onto this issue, it would be nice if I could run a Claude cover remote session as a system service instead of a terminal process that way I could have a long running remote session connection and just link up to my computer whenever I want to wherever I am without having to make sure that my remote session is actually running on my remote desktop

v2.1.80 — CLI mobile RC still broken. 10 consecutive versions (v2.1.71 → v2.1.80).

v2.1.80 changelog includes: "Fixed /remote-control appearing for gateway and third-party provider deployments where it cannot function." Meanwhile, CLI users where RC should function still can't connect from mobile.

Timeline:

• v2.1.79: VSCode /remote-control shipped and works — server-side infrastructure is functional
• v2.1.80: RC hidden from gateway/third-party deployments where it can't work
• v2.1.71 → v2.1.80: CLI claude remote-control mobile pairing broken across 10 consecutive versions

Both failure modes unchanged on Windows CLI + iPhone (iOS):

1. QR scan with Claude mobile app → app opens, nothing connects, no green dot
2. QR scan with device camera → opens App Store, then Claude app, no connection established

@antrewmorrison — you were assigned Mar 16. Any update on CLI mobile parity? The VSCode implementation proves the backend works. The remaining gap is CLI QR → mobile handshake.

v2.1.80 — tested immediately after upgrade. CLI mobile RC still broken.

Just updated to v2.1.80 and tested /remote-control (CLI, Windows). Both failure modes unchanged:

1. QR scan with Claude mobile app → app opens, nothing connects
2. QR scan with device camera → App Store → Claude app → no connection

10 consecutive broken versions. @antrewmorrison — any timeline?

v2.1.81 — tested immediately after upgrade. CLI mobile RC still broken. 11 consecutive versions.

v2.1.81 ships FOUR Remote Control improvements:

• Fixed /rename not syncing title for RC sessions
• Fixed RC sessions showing generic title instead of deriving from first prompt
• Fixed RC /exit not reliably archiving the session
• Improved RC session titles to refresh after third message

None of these fix CLI mobile pairing. QR scan from Claude iOS app → "Connecting..." indefinitely. Never establishes connection.

Windows CLI, iPhone iOS, same account, same network. 11 consecutive broken versions (v2.1.71 → v2.1.81).

@antrewmorrison — assigned since Mar 16, 4 versions ago. Is there a timeline for CLI mobile parity? The VSCode path works. The server infrastructure works. The gap is CLI QR → mobile handshake.

UPDATE: v2.1.81 — CLI mobile RC PARTIALLY WORKING.

Correcting my earlier report. After further testing:

• v2.1.81 sessions: mobile RC connects successfully ✅ — QR scan from Claude iOS app establishes connection
• v2.1.80 sessions: intermittent — some connect, some stuck on "Connecting..." indefinitely
• Pre-v2.1.80 sessions: still broken

This is real progress after 11 broken versions. Something in v2.1.80/81 improved the CLI handshake path. The inconsistency on v2.1.80 sessions suggests the fix may depend on session state or timing.

Platform: Windows CLI + iPhone iOS. @antrewmorrison — looks like your work is landing. The remaining gap is the v2.1.80 intermittent failures.

v2.1.81 — CLI mobile RC partially working but NOT STABLE.

After more testing over ~12 hours:

What works:

• Fresh v2.1.81 sessions can connect from mobile (first success in 11 versions)

What doesn't:

• Sessions that disconnect cannot reconnect — no reconnect mechanism visible in CLI
• Some sessions show "refreshed" status but mobile won't connect to them
• No /reconnect or equivalent command — once the connection drops, the session is orphaned from mobile
• Overnight sessions that were connected lost connection and could not re-establish

The missing piece: There's no way to re-pair a session from CLI after the initial QR connection drops. The v2.1.76 fix for "bridge sessions failing to recover after extended WebSocket disconnects" doesn't seem to apply to CLI sessions — or the recovery isn't surfaced to the user.

Expected behavior: Either (a) automatic reconnection when mobile app is reopened, or (b) a /reconnect or /rc command that regenerates the QR code for re-pairing.

Platform: Windows CLI + iPhone iOS, v2.1.81. @antrewmorrison

v2.1.81 update — RC reconnection still broken.

Continuing from my Mar 20 report. The initial v2.1.81 connection fix was real but short-lived:

• Fresh sessions can pair from mobile (confirmed)
• Disconnected sessions cannot reconnect — no mechanism to re-pair
• Sessions that show "refreshed" status on mobile still won't reconnect
• Running /remote-control again in an existing session does not regenerate a working QR code

The connection is single-use. Once it drops (phone sleeps, network blip, walk away for a bit), the session is permanently orphaned from mobile. There is no /reconnect command and the bridge recovery fix from v2.1.76 does not apply to CLI sessions.

For this to be usable, disconnected sessions need to automatically reconnect when the mobile app is reopened, or /remote-control needs to work as a re-pair command on existing sessions.

Platform: Windows CLI + iPhone iOS, v2.1.81. @antrewmorrison

Additional detail on reconnection failure:

When running /remote-control on a session that was previously connected, it displays the session URL. Pasting that URL into a browser — the same method that worked for initial connection — does nothing. Page loads but no session connects.

So both reconnection paths are dead:

1. QR scan on mobile → "Connecting..." forever
2. URL paste in browser → page loads, no session
3. No /reconnect command exists

The URL appears valid (same format as working initial connections), but the session bridge is gone and can't be re-established.

The QR-code-to-mobile-app flow for Remote Control is frustratingly fragile — I hit the same dead end with sessions that just never appear. pikiclaw takes a different approach: it keeps Claude Code running locally and pipes everything through Telegram (or Feishu/WeChat) as the transport layer, so there's no proprietary handshake to break — if your IM app works, the session works. Streaming output, multi-turn conversation, and file exchange all go through the chat. npx pikiclaw@latest to try it out.

GitHub: https://github.com/xiaotonng/pikiclaw

This is seriously broken. Can't open the chat on my iOS app at all.

Same symptom on Max plan.

• Claude Code CLI: 2.1.137
• iOS Claude app: 1.260430.0
• Plan: Max
• macOS: 24.6.0 (Darwin)

Repro:

1. /remote-control in CLI → fresh QR + URL generated
2. Open URL on iPhone (tried both QR scan and tapping URL from Messages)
3. App routes to Code context, shows brief "network error" toast, then "Loading messages" spinner that never resolves
4. CLI shows "Remote Control active" the entire time, no inbound activity logged

Ruled out:

• Reinstalled both apps
• Logged out/in on both sides
• Fresh session URL, opened within seconds
• Cellular only (Wi-Fi off), Tailscale off, iCloud Private Relay off
• Force-quit + reopen iOS app between attempts

Account auth: claude.ai OAuth (Max), same account on both sides.