Remote Control session not visible in session list, cannot reconnect after leaving

Also hitting this. When the remote session does connect, switching apps or navigating away on mobile loses the connection. The session doesn't appear in the session list. Tried resuming via the original link — doesn't reconnect, just opens a new unlinked thread. Effectively makes remote control unusable for anything beyond a single uninterrupted viewing.

Setup: Max plan, macOS, Claude Code CLI (npm-global).

Also hitting this. When the remote session does connect, switching apps or navigating away on mobile loses the connection. The session doesn't appear in the session list. Tried resuming via the original link — doesn't reconnect, just opens a new unlinked thread. Effectively makes remote control unusable for anything beyond a single uninterrupted viewing. Setup: Max plan, macOS, Claude Code CLI (npm-global).

Ditto

Same.

this issue is happening way too often, please fix this

same. Right now it's quite unstable, It usually can't last for 2-3 times check via mobile.

This happens with me both mobile and desktop.

same

Same issue. Mac Mini (always-on, macOS) running Claude Code CLI, connecting via Claude iOS app. Session works fine initially, but after 15-20 minutes idle (phone locked or app backgrounded), the session disappears entirely from the app. No way to reconnect without re-pairing from the terminal. Network stays up (Tailscale SSH still works). This makes remote control unusable for any workflow where you step away from the computer.

Same here : Session disconnects, making the feature unusable

This makes remote control unusable for any workflow where you step away from the computer.

Nothing says "remote control" quite like "…as long as you stay right here, at this desk, in front of this specific machine." Peak irony. 😄 Hope this gets fixed soon.

Same issue here, still happening.

I have the issue that I loose the connection / remote control stopps in claude code without any reason. the session is still visible in the session list on the mobile and I can open the session but when I send a prompt in the remote control I get the message that the session is not connected. The prompt is then lost :(.

In case there is a connection problem, the prompt/session should be kept in the mobile and a connection retry should happen, or a feedback to restart the remote control in claud code. A connection should be actively be closed. these "silent fails" are very frustrating.

Same issue

Same problem with me. Feature ist unusable this way.

Still experiencing all of the above on Claude Code 2.1.76 (Windows 11, npm global install).

Additional symptoms beyond session invisibility and reconnection failure:

• Plan Mode and skills loop endlessly. After a silent disconnect and apparent "reconnection," interactive features like Plan Mode interviews ask the same questions repeatedly. The session appears connected in the terminal, but the remote client is actually operating on a new, context-less session.
• Partial feature availability. Some features work after reconnect while others silently fail, making it difficult to tell whether you are genuinely reconnected or just in a broken state.

The core issue remains: the session looks connected from both ends, but the link is dead. There is no error, no notification, and no recovery path. You only discover it failed when your work doesn't stick.

I notice Remote Control continues to receive new features in recent releases, which is great, but the foundational session persistence and reconnection are still broken. It would be encouraging to see stability prioritised alongside feature development. Right now the feature is not reliably usable for its primary use case: checking in on a running session from a mobile device.

This is now fixed. 2.1.76

This is now fixed. 2.1.76

<img width="487" height="142" alt="Image" src="https://github.com/user-attachments/assets/47baf27f-df96-48a9-807c-1d77abf5bd4c" />

<img width="315" height="171" alt="Image" src="https://github.com/user-attachments/assets/b827dbb1-0150-4aad-8141-30f7bb053298" />

Still reproducible on v2.1.76 / Windows 11.

In my case the trigger is a system crash (BSOD) rather than intentional navigation away. After an unexpected reboot, the previous Remote Control sessions remain visible in the session list as apparently active, but they are all dead — the terminal process was killed by the crash, not by a clean Ctrl+C exit.

Environment:

• OS: Windows 11 Pro, Build 26200
• Claude Code: v2.1.76
• Client: claude.ai desktop (Remote Control panel)
• Trigger: BSOD → automatic reboot → relaunch Claude Code → stale sessions from previous run still visible

My workaround: Tell OpenClaw to start a new remote-control session 😉

Probably the same underlying bug as the OP, with a sharper repro that might help narrow the mechanism:

Symptom variant: the session does appear in the iOS list, but only while the model is actively generating. The moment the model finishes a turn and is idle, the session row and the "In progress" header disappear. Sending another message (from the CLI) brings both back for the duration of that turn, then they vanish again on completion.

Workaround: if you tap into the session row during a generation window, the detail view persists and you can keep using the session normally. It's only the list-level entry that's hidden between turns. This also tells us the session record is alive in the app's state — the list view is just filtering it out when the model is idle.

Hypothesis: the "In progress" group looks like it's keyed on model is currently generating rather than session is alive. The underlying session is fully healthy throughout — the remote-control web URL printed by /remote-control (claude.ai/code/session_…) stays reachable in a desktop browser the entire time, including when the iOS list shows nothing.

Repro:

1. Start a remote-control session from the CLI: /remote-control. Keep using the CLI as your input.
2. Open the Claude Code iOS app → Code tab.
3. Send a message in the CLI. While the model is generating, the "In progress" section is visible at the top of the iOS list with the session labeled.
4. As soon as the model finishes its turn, "In progress" + the session row disappear.
5. Send another message in the CLI → both reappear → vanish on completion. Repeat.

Environment (additional data point — OP was Win11):

• Host OS: macOS (Darwin 25.3.0)
• Claude Code CLI: 2.1.116
• iOS: 26.4.1
• Claude Code iOS app: 1.260416.0 (latest as of posting; bug still present after updating)
• Session started via /remote-control from the CLI, verified working both via the web URL and via the iOS app while it's visible.

(Note for triage: this issue is labeled area:cowork but the report — and this comment — is about /remote-control, which lives in CLI rather than the Cowork VM workspace feature. Other recent remote-control bug reports use area:cli or no area label. Might be worth relabeling.)

Adding a server-side data point since #29748 was closed as a duplicate of this and then locked: the reboot-persistence scenario it described is still unsolved.

Setup: claude remote-control --name container --remote-control-session-name-prefix container running as an OpenRC service on a headless Alpine VM, supervised by supervise-daemon (auto-restart on crash). Every supervisor respawn or host reboot creates a brand-new session ID — old session URLs become invalid, in-flight conversations on claude.ai/code can't be resumed, and stale "connected" sessions linger until they eventually time out. There's no path to navigate back into a session once you leave it, matching the original report.

A stable per-machine session identifier (e.g. --session-id <uuid> / --resume) would address both the "session disappears from list" issue here and the reboot-survival case from #29748. More detailed feature request: #36261.