Ways to run Claude Code in the cloud, so it keeps working when your laptop is closed

• For most people: Claude Code cloud sessions. They keep running after you close your laptop, at no extra VM charge¹.
• For recurring jobs: cloud scheduled tasks, now in research preview³.
• For full control: install Claude Code on your own Linux server⁴.
• For a cloud dev box per developer: GitHub Codespaces⁵, or Coder on your own infrastructure⁶.
• For agents inside your own product: a sandbox API such as E2B⁷.
• For a team that wants to run much more agent work off its laptops: Leverage Computer. Sessions keep going with laptops closed, start from webhooks, pull requests and schedules, and the team shares them, with rules on every tool call^{8, 13, 9, 10}.

1. Does it really keep going? Some options stop on idle or cap session length.
2. Machine size. CPU, memory and disk for your builds and tests.
3. Repository access. GitHub only, or anything with Git.
4. Who can see and continue the work. One person, or the team.
5. Cost. Included in your plan, by the hour, or by the second.

Claude Code cloud sessions: the default

Strengths

• Start from claude.ai/code, the Claude app, or the terminal with claude --cloud, and pull a session back with claude --teleport¹.
• "The session keeps running after you close your laptop"¹.
• Each session runs in an isolated, Anthropic-managed VM running Ubuntu 24.04^{1, 2}.

Weaknesses

• Cloning and pull requests in Anthropic-hosted environments need GitHub¹.
• "Cloud sessions stop after a period of inactivity and the session's VM is reclaimed"¹.
• Resources are "approximate resource ceilings that may change over time", and memory-heavy builds can be stopped².

Price. Included with Pro, Max, Ultra and Team plans, and Enterprise premium or Chat + Claude Code seats¹.

Cloud scheduled tasks: for recurring jobs

Strengths

• Run in the cloud "on a schedule, on API calls, or on GitHub events", so they keep working when your laptop is closed³.

Weaknesses

• "Scheduled tasks are in research preview"³.
• Schedules more frequent than once an hour are rejected³.
• They "belong to your individual claude.ai account" and are not shared with teammates³.

Price. Available on Pro, Max, Ultra, Team and Enterprise plans³.

Your own server: for full control

Strengths

• Claude Code runs on Ubuntu 20.04+, Debian 10+ or Alpine 3.19+ with 4 GB+ RAM⁴.
• Any repository host, any machine size, your own network.

Weaknesses

• You patch, secure and pay for the server, and keep the session alive yourself.
• Teammates cannot see the session unless you give them access to the machine.

Price. Your server, plus a Pro, Max, Ultra, Team, Enterprise or Console account⁴.

GitHub Codespaces: for a cloud dev box per developer

Strengths

• Machines from 2 to 32 cores, billed by the hour⁵.

Weaknesses

• Organization and enterprise plans "do not include a free quota"⁵.
• Each codespace belongs to one person; you still need a Claude plan inside it.

Price. $0.18 an hour for 2 cores up to $2.88 for 32 cores, plus $0.07 per GB-month of storage⁵.

Coder: for self-hosted dev environments

Strengths

• "Provision unlimited self-hosted workspaces on the infrastructure you already own"⁶.
• Runs "Claude Code, Codex, Cursor, and other AI coding agents" in its workspaces⁶.

Weaknesses

• Self-hosted only: you run the platform⁶.
• The Community and Premium plans allow up to 5 active Coder Agents⁶.

Price. Community is free; Premium is priced per user a year (no price on the page); AI Premium is custom⁶.

E2B: for running agents inside your own product

Strengths

• Gives "each agent session an isolated Linux machine", billed per second⁷.

Weaknesses

• A sandbox API for building your own product. It has no place for a team to work together.
• Sessions last up to 1 hour on Hobby and 24 hours on Pro⁷.

Price. Hobby $0 with a one-time $100 in credits; Pro $150 a month plus usage; $0.000014 per vCPU-second⁷.

Leverage Computer: for teams that run Claude Code or Codex every day and want to run much more of it

We make Leverage Computer. This section uses our own public pages, and it says where Leverage Computer does not fit.

Leverage Computer gives each agent session its own isolated VM with sudo, open internet, a terminal, a browser and a persistent disk, inside one workspace the team shares⁸.

Strengths

• Keeps working with every laptop closed, and sleeps when idle; a sleeping VM costs nothing⁸.
• Saved work. Every completed agent turn is saved to Git, and an archived session reopens with the same machine and files^{8, 12}.
• Shared live. Teammates can watch, steer, queue or stop a session⁹.
• Governed. Agents get a short-lived token, never your keys; sends, deletes and deploys wait for a person by default¹⁰.
• Scheduled work runs as a person, limited to the tools you choose¹³.
• Session view. In the app, a session shows the conversation, its files and a terminal side by side⁸.
• Your own environments. Set variables and secrets and pick them per space or session. A secret can be added to HTTPS headers by the network, so its value never enters the VM⁸.

Where Leverage Computer is the wrong choice

• You need more than 8 CPUs and 16 GB per session. Large is our biggest machine⁸.
• Code must run on your own servers. Leverage Computer does not offer a self-hosted version; consider your own server or Coder.
• You only want one background task now and then. Cloud sessions in your Claude plan cost nothing extra¹.

Price. $0.50 per agent hour on Standard (2 CPU, 4 GB), $1.00 Medium (4 CPU, 8 GB), $2.00 Large (8 CPU, 16 GB). Use your own Claude plan or credits^{11, 8}.

Inside one Leverage Computer session

People

Watch it live

Steer or queue a message

Approve tool calls

Share as viewer or collaborator

Environment

Variables per space or session

Secrets added at the network

Values hidden from transcripts

The computer

Its own VM with sudo

Claude Code, Codex or Grok Build

Sleeps when idle

terminalbrowserfilesdisk

Git

Every turn committed

Team memory and skills

What it makes

Pull requests with Auto-fix

Private preview links

Published pages

Scheduled and event runs

1. Just want work to continue overnight? Claude Code cloud sessions¹.
2. Need a specific machine, network or repository host? Your own server or Coder^{4, 6}.
3. Building a product that runs agents for your users? A sandbox API such as E2B⁷.
4. A team sharing agents, files and approvals? Leverage Computer^{8, 9, 10}.

• How to run Claude Code for a whole team: your options compared
• How to share Claude Code sessions with your team
• Devin alternatives for small engineering teams
• The computer underneath
• Always on: automations
• Pricing
• All comparisons