Claude Code Remote Control keeps disconnecting: causes and fixes

You start a session with Remote Control, walk away, and later the Claude app says Remote Control disconnected, or Can't reach, or your message fails with "An unknown network error has occurred". Back at the computer, the terminal may say everything is fine.

The short answer

Remote Control is a live connection from the Claude app to a claude process on your computer. It drops when one of these happens:

1. The computer sleeps (lid closed, idle sleep, battery saver).
2. The network changes (Wi-Fi switch, VPN on or off, a long outage).
3. The process stops (terminal closed, Desktop app or VS Code quit, SSH window closed, a crash).
4. The saved Claude login can't be renewed.
5. The session goes idle and the server drops it. People report this even with the computer awake.

For 1 to 4 there is a fix below. For 5, the fix today is to reconnect by hand, and to keep Claude Code updated.

The universal reconnect, in an interactive session on the computer:

/remote-control

What people report

• #34255: "automatic reconnection doesn't work -- connection drops silently with no recovery". One recent reply shows Remote Control disconnected — Transport recovery exhausted (code 4093) — run /remote-control to reconnect.
• #32982: "Remote Control sessions die after ~20 min idle". The phone shows "Failed to send message — An unknown network error has occurred" while the CLI still says Remote Control is active. Later replies confirm it on newer versions, on Mac, Windows and Debian.
• #33041: drops every few minutes, with sleep already turned off and a VPN tried.

First, find out which state you're in

The Remote Control docs say the app's "disconnected" message doesn't tell you whether Claude is still working. Look at the computer:

• The terminal shows a disconnect line, starting Remote Control disconnected: it names the reason. Follow it, usually /login and then /remote-control.
• Claude Code is running and shows no failure: an interactive session reconnects by itself once the machine is awake and online. Wait a minute.
• Claude Code isn't running: start it again and bring the session back (below).

For more detail, start server mode with logs:

claude remote-control --verbose

Cause 1: the computer slept

Docs: "if your laptop sleeps or your network drops, Claude Code reconnects automatically when your machine comes back online." Nothing runs while it sleeps, though. The fix is to stop the sleep.

macOS. Keep the Mac awake for as long as Claude runs:

caffeinate -dims claude --remote-control

Closing the lid still sleeps a MacBook unless it's in clamshell mode with power and a display. For a Mac on a desk, stop idle sleep on the charger with sudo pmset -c sleep 0. pmset -g assertions shows what's holding it awake.

Windows. Turn off sleep while plugged in, from an admin terminal:

powercfg /change standby-timeout-ac 0

Also set "When I close the lid" to "Do nothing" under Power Options if you use a laptop closed.

Linux. Block idle sleep for the life of the process:

systemd-inhibit --what=idle:sleep claude --remote-control

On a laptop, set HandleLidSwitch=ignore in /etc/systemd/logind.conf if it should stay on with the lid shut.

Cause 2: the network changed

Two documented behaviors:

• After a VPN or network change, if something answers with HTTP 403, Claude Code keeps retrying for up to three minutes, then disconnects and names what refused (a network edge, or a proxy, VPN or firewall).
• During a long outage, an interactive session keeps retrying and reconnects on its own. Server mode (claude remote-control) gives up after roughly 10 minutes and exits.

So on a flaky connection, prefer claude --remote-control (interactive) over server mode. If you see could not reach the Remote Control server for about 30 minutes, run /remote-control.

Cause 3: the process stopped

Closing the terminal, quitting the Desktop app or VS Code, or closing an SSH window ends the session. On a remote machine, always start Claude inside tmux:

tmux new -s claude
claude remote-control

Detach with Ctrl-b d. To bring sessions back after the server stopped, run this in the same folder within about four hours:

claude remote-control --continue

For a session you started with claude --remote-control or /remote-control, resume it with claude --continue, then run /remote-control. In server mode, a crashed session comes back when you message it from the phone (v2.1.238 or later).

Some users in #32982 report sessions started from the Claude Desktop app on Windows drop after a few hours, while the same thing started from a PowerShell terminal holds. Worth trying if you're on Desktop.

Cause 4: the login ran out

Remote Control runs on short-lived credentials renewed from your saved claude.ai login. When that login expires you get something like:

Remote Control disconnected — Claude.ai login expired — run /login to restore Remote Control

Run /login, then /remote-control if the message says so. Claude Code warns three days ahead at startup ("Your login expires in 3 days"), but only when you start it, so an unattended session can miss it. More in the headless login guide.

Cause 5: idle drops with the computer awake

This is #32982. With the machine awake and online, people still see idle sessions dropped server-side. There's no documented setting that stops it. What helps:

• Update: claude update. Reconnect handling has changed a lot across 2.1.x.
• Reconnect with /remote-control when it happens.
• Add your version and OS to #32982 rather than a new issue.

Related fixes

• "Remote Control environments are not available for your account": when it won't start at all.
• Claude Code login on a headless server: signing in on a box with no browser.
• Running Claude Code on a server: moving Claude off the laptop.

If you'd rather not keep a machine awake

Most of this page is about keeping one computer awake, online and signed in. Podway is an always-on cloud computer for Claude Code, so causes 1 and 3 mostly go away. You use your own Pro or Max plan and open the session from the Claude app via Remote Control. If the agent crashes, Podway restarts it and reconnects Remote Control. Before your Claude login expires, Podway tells you, with a one-click reconnect. On Team or Enterprise, your org Owner still needs to enable Remote Control.

Your first pod is free, no card needed, and pods start at $4/month. Start a pod, or see the agent computer page.