Claude Code on a server, unattended.
Claude Code on a server, working while you sleep, reachable from your phone. Most guides for this are wrong in the same two ways: they send you to a VPS you may not need, and they hand you an npm workaround that stopped working in January.
30–60 min for a working box · 2–4 hrs with real isolation
Decide you actually need this
Anthropic now runs the two things most people build a VPS for. This step exists to end the project if it should end.
~10 min
- Claude Code on the web runs every session in an isolated Anthropic-managed VM, with a network proxy enforcing a default allowlist and your GitHub token held outside the sandbox. Needs a Claude subscription, no infrastructure.
- Routines run Claude Code on a schedule, on an API call, or reacting to GitHub events, on Anthropic's infrastructure. This is the hosted version of the cron-in-tmux setup most VPS guides are really building.
- Remote Control continues a local session from your phone or browser. If the actual want was "check on it from my phone", that is this, and it needs no server.
Stop and think
Build the VPS only if you need your own environment, your own private network, or a long-lived box that is yours. If what you wanted was a scheduler or a phone client, two of those already exist and someone else maintains them.
Tick before moving on
The setup is not the hard part. The hard part is being honest about whether you need it, picking a CPU profile that exposes real instructions, and putting a boundary around the agent before you take the prompts away.