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

> Seven places to run Claude Code off your laptop, from Anthropic's cloud sessions to your own server.

By Eimen, founder of Leverage Computer. Last reviewed 12 November 2026.

Disclosure: We make Leverage Computer, one of the tools on this page. We describe every product, ours included, from its own public pages, and each fact links to its source. Prices change: check the linked page before you buy. Found something wrong or out of date? Email [founders@leverage.computer](mailto:founders@leverage.computer) and we will fix it.

## The short answer

- **For most people: Claude Code cloud sessions.** They keep running after you close your laptop, at no extra VM charge [1].
- **For recurring jobs:** cloud scheduled tasks, now in research preview [3].
- **For full control:** install Claude Code on your own Linux server [4].
- **For a cloud dev box per developer:** GitHub Codespaces [5], or Coder on your own infrastructure [6].
- **For agents inside your own product:** a sandbox API such as E2B [7].
- **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].

**Figure: One day: start at 10, close the laptop at 6.** Cloud sessions keep going after the laptop closes, then stop when idle [1]. A Leverage Computer VM sleeps instead, and wakes with its disk when there is work [8].

- In your terminal: running, stops with the laptop
- Cloud session: keeps running, stops when idle
- Your own server: runs while you keep it up
- Leverage Computer: running, asleep, wakes

## What to check

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.

## Side by side

|  | Keeps working with the laptop closed | Machine | Limits worth knowing | Price |
| --- | --- | --- | --- | --- |
| Claude Code cloud sessions | Yes [1] | About 4 vCPUs, 16 GB RAM, 30 GB disk [2] | GitHub for clone and pull requests; stops after inactivity [1] | Included in Pro, Max, Ultra and Team; no separate VM charge [1] |
| Cloud scheduled tasks | Yes [3] | Same cloud VMs | Research preview; at most once an hour; tied to one person's account [3] | Included in paid plans [3] |
| Your own server | Yes, if you keep it running | Your choice; Claude Code needs 4 GB+ RAM [4] | You maintain it | Your server, plus a Claude plan [4] |
| GitHub Codespaces | Not checked | 2 to 32 cores [5] | No free quota for organizations [5] | From $0.18 an hour per 2-core machine [5] |
| Coder | Not checked | Your infrastructure [6] | Self-hosted only [6] | Community edition free; Premium priced per user a year [6] |
| E2B | Up to 24 hours per session on Pro [7] | Billed per vCPU and RAM second [7] | A sandbox API for your own code, not a dev environment | Hobby $0 with $100 one-time credits; Pro $150 a month plus usage [7] |
| Leverage Computer | Yes [8] | 2 CPU/4 GB, 4/8 or 8/16, persistent disk [8] | Sleeps when idle and wakes when there is work [8] | $0.50 per agent hour on Standard [11] |

"Not checked" means we did not verify that behavior for this page.

## The options

### 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` [1].
- "The session keeps running after you close your laptop" [1].
- 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 [1].
- "Cloud sessions stop after a period of inactivity and the session's VM is reclaimed" [1].
- Resources are "approximate resource ceilings that may change over time", and memory-heavy builds can be stopped [2].

**Price.** Included with Pro, Max, Ultra and Team plans, and Enterprise premium or Chat + Claude Code seats [1].

### 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 [3].

**Weaknesses**

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

**Price.** Available on Pro, Max, Ultra, Team and Enterprise plans [3].

### Your own server: for full control

**Strengths**

- Claude Code runs on Ubuntu 20.04+, Debian 10+ or Alpine 3.19+ with 4 GB+ RAM [4].
- 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 [4].

### GitHub Codespaces: for a cloud dev box per developer

**Strengths**

- Machines from 2 to 32 cores, billed by the hour [5].

**Weaknesses**

- Organization and enterprise plans "do not include a free quota" [5].
- 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 [5].

### Coder: for self-hosted dev environments

**Strengths**

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

**Weaknesses**

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

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

### E2B: for running agents inside your own product

**Strengths**

- Gives "each agent session an isolated Linux machine", billed per second [7].

**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 [7].

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

### 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 [8].

**Strengths**

- **Keeps working with every laptop closed**, and sleeps when idle; a sleeping VM costs nothing [8].
- **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 [9].
- **Governed.** Agents get a short-lived token, never your keys; sends, deletes and deploys wait for a person by default [10].
- **Scheduled work runs as a person**, limited to the tools you choose [13].
- **Session view.** In the app, a session shows the conversation, its files and a terminal side by side [8].
- **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 [8].

**Where Leverage Computer is the wrong choice**

- **You need more than 8 CPUs and 16 GB per session.** Large is our biggest machine [8].
- **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 [1].

**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].

## How to choose

1. **Just want work to continue overnight?** Claude Code cloud sessions [1].
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 [7].
4. **A team sharing agents, files and approvals?** Leverage Computer [8][9][10].

## Questions

**Can Claude Code run in the cloud?**
Yes. Cloud sessions run on Anthropic-managed VMs and keep running after you close your laptop. They are included with Pro, Max, Ultra and Team plans [1].

**How big is the Claude Code cloud VM?**
About 4 vCPUs, 16 GB of RAM and 30 GB of disk, described as approximate ceilings that may change [2].

**Does Claude Code in the cloud work without GitHub?**
Cloning and pull requests in Anthropic-hosted environments need GitHub. Other repositories can be sent as a bundle, but the session cannot push back to them [1].

## Sources

Checked on 12 November 2026.

1. Claude Code docs, cloud sessions: https://code.claude.com/docs/en/claude-code-on-the-web
2. Claude Code docs, cloud environments: https://code.claude.com/docs/en/cloud-environments
3. Claude Code docs, scheduled tasks: https://code.claude.com/docs/en/routines
4. Claude Code docs, setup: https://code.claude.com/docs/en/setup
5. GitHub Docs, Codespaces billing: https://docs.github.com/en/billing/concepts/product-billing/github-codespaces
6. Coder, pricing: https://coder.com/pricing
7. E2B, pricing: https://e2b.dev/pricing
8. Leverage Computer, the computer underneath: https://leverage.computer/compute/
9. Leverage Computer, work in the open: https://leverage.computer/teams/
10. Leverage Computer, AI governance: https://leverage.computer/governance/
11. Leverage Computer, pricing: https://leverage.computer/pricing/
12. Leverage Computer, Git under everything: https://leverage.computer/git/
13. Leverage Computer, automations: https://leverage.computer/automations/

[Get started](https://app.leverage.computer/login?mode=signup&utm_source=leverage.computer&utm_medium=markdown&utm_content=/compare/run-claude-code-in-the-cloud/)

## More

- [How to run Claude Code for a whole team: your options compared](https://leverage.computer/compare/claude-code-for-teams/)
- [How to share Claude Code sessions with your team](https://leverage.computer/compare/share-claude-code-sessions/)
- [Devin alternatives for small engineering teams](https://leverage.computer/compare/devin-alternatives/)
- [The computer underneath](https://leverage.computer/compute/)
- [Always on: automations](https://leverage.computer/automations/)
- [Pricing](https://leverage.computer/pricing/)
- [All comparisons](https://leverage.computer/compare/)