All posts
Troubleshooting

Keep your mobile coding session alive while you're away

June 27, 2026 · 4 min read

Why a CodeMote session needs the computer awake, and how to stop your Mac, Windows or Linux machine from sleeping so long-running agents and terminals keep streaming.

CodeMote controls the VS Code on your real machine — nothing runs in the cloud on your behalf, which is exactly what keeps your code private. The trade-off: if that computer goes to sleep, the tunnel drops and your terminals and agents pause until it wakes. Here is how to keep a long task running while you step away with just your phone.

macOS — caffeinate

The simplest fix is built in. Before you leave, start your work under caffeinate, which keeps the Mac awake until the command finishes:

$caffeinate -s claude

Or keep the whole machine awake for a few hours regardless of what you’re running:

$caffeinate -t 14400

macOS — power settings

For a permanent change on a desk machine, set the display to sleep but keep the system awake on power, in System Settings → Displays → Advanced, or via pmset.

Windows and Linux

  • Windows— set Sleep to “Never” while plugged in under Settings → System → Power, or use a keep-awake utility for the session.
  • Linux — disable suspend for the session, e.g. systemd-inhibit --what=sleep claude, or adjust your power settings.
Keep VS Code open and the session started while you’re away. Closing the lid on a laptop still suspends most machines even with these settings — for travelling, leave the laptop open or plugged in at a desk.

With the machine awake, persistent shells and agents stream straight to your phone for as long as you need. More in the FAQ.

Take your dev environment with you.

Drive your AI agents, terminals and Git from your phone — with no cloud copy of your code.

Get the app