Run coding agents overnight, unattended

Sessions that outlive your screen

A CodeMote agent chat runs on the host machine, not in your browser. Close the laptop, kill the tab, switch devices: the session keeps its history and its running state, because clients are remote controls, not containers. Reopen the workspace from any browser (or the iOS app) and you are looking at the same chat, mid-thought.

Answer from wherever you are

When the agent hits a tool approval or asks a question, that request waits for you in the workspace. On iPhone, a Live Activity pings you the moment attention is actually needed, so the ten seconds happen on the sofa instead of forcing a trip back to the desk. Approve, answer, and the agent carries on.

Schedule the boring runs

Some agent work shouldn’t need a prompt at all. Standing jobs run agents on a schedule: the nightly triage of new issues, the recurring dependency check, the morning summary of what changed. The job runs whether you are awake or not, and its transcript is waiting in the workspace when you are.

The guardrails stay on

Unattended does not mean unsupervised. Tool approvals still gate what the agent may do, questions still wait for a human answer, and the morning review is a real one: the workspace’s git view shows every diff, and pull requests go from open to merge without leaving the browser. You are removing the chair-time, not the judgment.

The practical setup

Overnight work wants a machine that stays awake: a desktop that doesn’t sleep, or better, a VPS (the VPS setup guide covers it end to end). Start the host in tmux so it outlives your SSH session, and switch the tunnel to a longer-lived provider for multi-day runs:

The default Cloudflare quick tunnel is built for sessions; --help lists the providers built for weeks.