Claude Code Remote Control does not reconnect after a drop; mobile session stays stuck
Remote Control in Claude Code loses its connection to the Claude mobile app during long or idle sessions and does not recover on its own. The phone stops getting responses, and the terminal shows 'Remote Control reconnecting' indefinitely. Reports come from macOS, Linux, WSL2 and Windows on Claude Code versions 2.1.76 to 2.1.81.
Originally asked on GitHub: https://github.com/anthropics/claude-code/issues/34255
6 answers
Status: open. As of the latest comments in this thread, there is no maintainer response and no automatic recovery for Remote Control reconnection.
The workaround reported in the thread is manual. In the terminal running Claude Code, run /remote-control, choose 'Disconnect this session' from the menu, then run /remote-control [session-name] again. The issue author says the connection came back healthy after this cycle every time, but it requires physical access to the machine.
One Linux user posted a systemd approach: a user timer every 5 minutes checks whether the Claude process has an ESTAB TCP connection on port 443, using ss against the service's MainPID. If there is none on two consecutive checks (about 10 minutes), the service is restarted. The poster notes that restarting creates a new session and loses conversation history, so they describe it as a last resort rather than a fix.
Other reported symptoms include the mobile app showing the session as active while messages are not processed, and the terminal staying on 'Remote Control reconnecting'. Reporters have requested a non-interactive reconnect flag, a heartbeat-based status indicator, and a visible disconnected state on mobile. The thread does not mention any such flag existing.
Did this work for you?What a GitHub user tried on GitHub (Worked)
The issue author ran /remote-control, selected 'Disconnect this session' in the TUI menu, then ran /remote-control [session-name] again. The author reports this restored the connection each time.
Source: https://github.com/anthropics/claude-code/issues/34255 (opens external site)
Did this work for you?What @SerkanGezici tried on GitHub (Worked)
A WSL2 user with Claude Code v2.1.76 ran /remote-control, selected Disconnect, then ran /remote-control again and chose Connect. The thread calls this the only workaround and notes it requires access to the PC terminal.
Source: https://github.com/anthropics/claude-code/issues/34255#issuecomment-4067747052 (opens external site)
Did this work for you?What @henrikalthofknudsen tried on GitHub (Outcome unclear)
A Linux user set up a systemd user service and a timer running every 5 minutes. It checks for an ESTAB connection on port 443 for the service's MainPID using ss, and restarts the service after two consecutive checks with no connection.
Source: https://github.com/anthropics/claude-code/issues/34255#issuecomment-4102743990 (opens external site)
Did this work for you?What @Wingie tried on GitHub (Didn't work)
A Linux user tried a loop-restart approach that restarts Claude Code automatically. It did not help because each restart creates a new session, which still requires manually reconnecting on the phone.
Source: https://github.com/anthropics/claude-code/issues/34255#issuecomment-4066540803 (opens external site)
Did this work for you?What @biguscj7 tried on GitHub (Didn't work)
A commenter ran /remote-control while the terminal showed 'Remote Control reconnecting'. It did not correct the failed connection. Continuing the session from iTerm2 also did not reconnect it.
Source: https://github.com/anthropics/claude-code/issues/34255#issuecomment-4061255395 (opens external site)
Did this work for you?