Claude Code runs on your laptop, so when you close the lid, it stops. To keep it working while you're away, or to start a task from your phone, you need Claude Code on a machine that isn't yours to carry around. There are three ways to get one in 2026.
We make BoxCompute, which is one of the three, so read with that in mind. Everything about Anthropic's products comes from its own documentation, read on 18 November 2026 and linked at the end.
The short version
- Your work is a GitHub repository and fits in sessions: Anthropic's cloud sessions. They come with Pro, Max, Ultra and Team plans.
- It has to run all day, every day, for the lowest price: a VPS you run yourself.
- You want a computer that keeps everything you set up, starts again when you message it, opens preview links and stays in Malaysia: a BoxCompute computer.
At a glance
| The machine | What it keeps | When it stops | Who looks after it | What you pay for the machine | |
|---|---|---|---|---|---|
| Anthropic cloud sessions | A fresh Ubuntu 24.04 VM per session, about 4 vCPUs, 16 GB of RAM and 30 GB of disk | Each session starts from a fresh clone of your GitHub repository; files are kept while it's paused, until the VM is reclaimed | Pauses after a few minutes without activity | Anthropic | Your Claude plan |
| Your own VPS | Whatever you rent; Claude Code needs 4 GB of RAM or more | Everything, until you delete the server | When you stop it | You: updates, firewall, backups | The provider's monthly price |
| BoxCompute computer | A full Linux VM with root, in Cyberjaya, Malaysia | The whole disk, until you delete the computer | After 30 idle minutes, unless a schedule keeps it on; a maintenance restart after about 42 hours | BoxCompute runs the machine; what's on it is yours | By the second while it runs, $0.05 to $0.80 an hour by size |
In all three, Claude Code signs in with your own Claude account and its usage counts against your plan.
1. Anthropic's cloud sessions
Anthropic runs Claude Code for you. Start a session at claude.ai/code, in the Claude app, or from your terminal with claude --cloud "Fix the flaky test in auth.spec.ts". Each session gets a fresh virtual machine running Ubuntu 24.04, with your repository cloned and common toolchains installed, at about 4 vCPUs, 16 GB of RAM and 30 GB of disk. Cloud sessions are available on Pro, Max, Ultra and Team plans, and to Enterprise users with premium seats or Chat + Claude Code seats.
Two things shape what it's good for. First, a session starts from a fresh clone of your repository, and cloning needs GitHub: anything you set up only on your own machine isn't there. Second, after a few minutes without activity, the VM pauses with its files saved, and a paused VM can later be reclaimed. Reopening the session then builds a fresh VM: your conversation comes back, but shell commands that were still running in the background don't.
Choose it when the work lives in a GitHub repository and fits into sessions: fix this bug, write these tests, open a pull request.
If what you want is your own laptop's session on your phone, that's Remote Control instead. It shows a session on claude.ai/code and in the Claude app, but Claude keeps running on your machine the whole time, so your laptop has to stay on.
2. A VPS you run yourself
Rent a Linux server, install Claude Code, sign in with your own Claude account and keep it running in tmux so it survives a dropped connection. Anthropic lists Ubuntu 20.04 or newer, or Debian 10 or newer, and at least 4 GB of RAM. Smaller servers are where the installer runs out of memory.
This is the cheapest way to have Claude Code running around the clock, and nothing is ever wiped. The cost is that you're now a system administrator: security updates, a firewall, SSH keys and backups are yours. Nothing gives you a link to the app it just started, or a way to talk to it from your phone, unless you build that too.
3. A BoxCompute computer
A BoxCompute computer is a full Linux VM with root access, hosted in Cyberjaya, Malaysia. Its disk is kept when it stops, so whatever Claude Code installs or builds is there next time. There are two ways to put Claude Code on it:
- In the computer's terminal. On the computer's page, open Overview → Agents on this computer and choose Install for Claude Code. It uses Anthropic's own installer. Then choose Open terminal, run
claudeand sign in. The sign-in stays in the VM. - In a chat. In the BoxCompute app, pick Your Claude plan in a chat's model menu. The first time, the chat installs Claude Code in its computer and shows a sign-in card. You sign in on Anthropic's own page and paste the code back. After that, each message you type goes to Claude Code, and its work shows up in the chat, from a laptop or a phone's browser.
Either way, it's Anthropic's unmodified Claude Code, signed in with your own plan. BoxCompute never reads or stores that sign-in, your Claude usage counts against your plan, and BoxCompute bills only for the time the computer runs. When Claude Code starts a web app, the computer can give you a preview link to open it from anywhere.
When it stops. A computer stops 30 minutes after it was last used and keeps its files. The next message from the chat starts it again. To keep it running during your working hours, give it a schedule with a running window. Starter also has Always on, which keeps a computer up and starts it again after the maintenance restart that comes after about 42 hours of continuous uptime. A restart still ends programs that were running, so this is not the same as a server that never reboots.
Which size. Claude Code lists 4 GB of RAM. On BoxCompute that's XL: 4 CPUs and 8 GiB at about $0.40 an hour, which comes with Starter. Small (0.5 CPU, 1 GiB, $0.05 an hour) and Large (1.5 CPU, 3 GiB, $0.15 an hour) are below that. A short session can work there, but a long one can run out of memory.
What it costs to keep it on
Your Claude plan costs the same in all three. The difference is the machine.
A BoxCompute XL that runs three hours each working day, about 22 days a month, costs about $26 a month. Left on around the clock, the same XL costs about $288 a month, which is far more than a VPS. BoxCompute is built to be there when you message it and to cost nothing while it's stopped, not to be the cheapest always-on server. If Claude Code really has to run 24 hours a day, rent a VPS.
Signing in, and Anthropic's terms
Sign in yourself, with your own account, wherever Claude Code runs. Anthropic's terms forbid third-party developers to "route requests through Free, Pro, Max, or Ultra plan credentials on behalf of their users". They also say that this does not "prevent an end user from signing in to the unmodified Claude Code binary with their own Claude subscription, including where a platform hosts Claude Code".
The same page notes that "Advertised usage limits for Pro, Max, and Ultra plans assume ordinary, individual usage". For work that runs on a timer with nobody typing, use an API key rather than a plan. BoxCompute's chat sends Claude Code only the messages you type. Scheduled prompts in BoxCompute run on BoxCompute's own agent, never on your Claude plan.
Sources
Read on 18 November 2026:
- Claude Code on the web: code.claude.com/docs/en/claude-code-on-the-web
- Cloud environments, VM size and idle behaviour: code.claude.com/docs/en/cloud-environments
- Remote Control: code.claude.com/docs/en/remote-control
- System requirements: code.claude.com/docs/en/setup
- Installs killed on low-memory servers: code.claude.com/docs/en/troubleshoot-install
- Legal and compliance, including authentication and hosted Claude Code: code.claude.com/docs/en/legal-and-compliance
- BoxCompute computers, sizes, schedules and Always on: boxcompute.ai/docs/vm-sandbox-beta
- BoxCompute pricing: boxcompute.ai/pricing