Remote Control shows sessions as "Disconnected" while the local claude.exe process is still running

Description

Sessions enabled with Remote Control (/remote-control) intermittently show as
"Disconnected" in the Claude mobile app's Code tab, even though the underlying
local claude process is still running on the desktop.

Observed behavior

• Yesterday, before leaving the desktop, all Remote-Control-enabled sessions

showed as "Connected" in the mobile app.

• Today, away from the desktop, the mobile app shows:
• 2 sessions "Connected" — both are sessions I am *currently actively

chatting with via the mobile app* (last activity 5 min / 9 min ago).

• 4 sessions "Disconnected" — all sessions with no recent mobile-side

activity (last activity 17h / 17h / 21h / 1d ago), from earlier the
same day or the previous day.

• I checked tasklist on the desktop (Windows 11) and confirmed **19

claude.exe processes are currently running**, well more than the number
of sessions shown as "Connected." This suggests the disconnect is not
simply caused by the local process exiting (e.g. terminal closed).

• This makes it look like "Connected" status correlates with *recent active

chat from the mobile/web side*, not with whether the local process is
alive — which contradicts the documented behavior that Remote Control
should persist independent of active conversation
(https://code.claude.com/docs/en/remote-control), and should only time
out after ~10 minutes of the desktop machine being unreachable on the
network.

Expected behavior

A Remote-Control-enabled session with a live local process should continue
showing as "Connected" regardless of whether there has been recent chat
activity, per the documented behavior.

Environment

• OS: Windows 11 Pro
• Claude mobile app (Android)
• Remote Control enabled via in-session /remote-control