# Cloud Machines

This page explains the life of a cmux Cloud machine: how to create it, what sizes you can choose, how plan limits apply, and how to pause, snapshot, fork, and delete it.

## Create a machine

In the app, use File › New Cloud Machine (⇧⌘Y), the plus-button menu, the command palette, or the plus button in the Cloud sidebar. The sheet asks for a size and an optional label.

From the CLI, cmux vm new creates a machine and opens a workspace on it. Use --detach to create it without opening anything. If a create request is retried, cmux reuses the same request so you do not get two machines.

```
cmux vm new
cmux vm new --size 16g --name "search index"
cmux vm new --detach --json
```

If creation fails, the notification lets you retry, show the error, or copy it for a support request.

## Sizes

Each size sets memory, vCPU, and disk together. Pick a size in the create sheet or with --size. Pro and Team support 4g, 8g, and 16g (2, 4, and 8 vCPU). Max also unlocks 24g and 32g (12 and 16 vCPU), plus 64g (32 vCPU).

| Size | Memory | vCPU | Disk | Plan |
| --- | --- | --- | --- | --- |
| `4g` | 4 GB | 2 | 16 GB | Paid plans |
| `8g` | 8 GB | 4 | 32 GB | Paid plans |
| `16g` | 16 GB | 8 | 64 GB | Paid plans |
| `24g` | 24 GB | 12 | 96 GB | Max |
| `32g` | 32 GB | 16 | 128 GB | Max |
| `64g` | 64 GB | 32 | 128 GB | Max |

New machines use 8 GB of memory when you do not choose a size. Run cmux vm ls --json to see the sizes that your plan allows.

## Plan limits

Your active machines share one pool of vCPUs and memory. Run one large machine or several small ones. Paused machines do not use the pool. Disk is set for each machine and is not pooled.

-   Free accounts cannot create machines.
-   Pro and Founder's Edition accounts can have up to 5 active machines that share 20 vCPUs and 40 GB of memory. A machine is active while it is running or starting.
-   Team accounts can have up to 5 active machines for each paid seat. Each paid seat adds 20 vCPUs and 40 GB of memory to the team's pool.
-   Max accounts can have up to 5 active machines that share 80 vCPUs and 160 GB of memory. One Max machine can use up to 64 GB and 32 vCPUs, including the 24 GB / 12 vCPU and 32 GB / 16 vCPU sizes; Pro and Team stop at 16 GB and 8 vCPUs.
-   If a new, resumed, resized, or forked machine would go over the pool, cmux refuses the request and shows how much of the pool is in use. Pause or delete a machine to free resources, or upgrade to Max.
-   A machine larger than your plan allows is locked. You can list and delete it, but you cannot open it, run commands on it, resume it, or resize it until you upgrade.

See the pricing page for current prices. There is no metering and no overage billing.

## Keep coding agents up to date

With this setting on, the machine updates Claude Code, Codex, OpenCode, pi, and agent-browser. It checks after the machine is created and each time you connect, at most once every 24 hours. The update runs detached, so it never blocks connecting.

Each tool comes from its official GitHub release and is verified against the release asset's sha256 digest. npm is not used. A release installs only after it has been public for 3 days, and an update never installs an older version. A running agent keeps the files it started with, and a failed update leaves the current version in place.

The result of the last check is in /etc/cmux/agent-updates.state, and the updater's log is /var/log/cmux-agent-updates.log. A failed check runs again on the next connect.

```
cat /etc/cmux/agent-updates.state
tail /var/log/cmux-agent-updates.log
```

The New Machine sheet turns this on by default. To change it for an existing machine, right-click the machine and choose Keep Agents Up to Date, or run cmux vm agent-updates. cmux vm new keeps the image's versions unless you pass --agent-updates latest. Turning updates off keeps the versions already installed.

```
cmux vm new --agent-updates latest
cmux vm agent-updates brave-otter
cmux vm agent-updates brave-otter image
```

Updates use only github.com, api.github.com, objects.githubusercontent.com, and release-assets.githubusercontent.com. cmux allows these hosts in every network mode, including Allowlist and No internet, so a network policy never blocks updates.

## Resize

You can make a machine larger without data loss. Right-click the machine and choose Resize machine, or use cmux vm resize. Resize can only grow a machine. Disk grows in 4 GB steps up to 128 GB on Pro and Team, or 256 GB on Max (Go is limited to 16 GB). Memory grows up to 16 GB and CPU up to 8 vCPU on Pro, Team, and Founder's Edition, or up to 64 GB and 32 vCPU on Max. A larger machine uses more of your pool. Your plan sets the real maximum.

```
cmux vm resize brave-otter --memory 16G
cmux vm resize brave-otter --cpu 8 --disk 128G
```

## Pause and resume

cmux vm pause stops the machine's compute. The disk, workspaces, and terminal history stay. Running processes stop. cmux vm resume starts the machine again. Opening a paused machine or running a command on it also starts it.

Machines do not pause by themselves when they are idle. A machine keeps running until you pause it or delete it.

```
cmux vm pause brave-otter
cmux vm resume brave-otter
cmux vm wait brave-otter --wake --timeout 180
```

cmux vm wait waits until a machine is ready. Add --wake to start a paused machine first. This is useful in scripts before the first command.

## Checkpoints, forks, and restore

A checkpoint saves the machine's disk. A fork makes a new machine from the current state of a machine. Restore makes a new machine from a checkpoint. Checkpoints include the machine's environment file.

Use a checkpoint before a risky change, and use a fork to try two approaches in parallel from the same starting point.

```
cmux vm checkpoint brave-otter --name before-migration
cmux vm snapshot ls brave-otter
cmux vm restore <snapshot-id>
cmux vm fork brave-otter --name try-b
cmux vm snapshot rm brave-otter <snapshot-id>
```

Checkpoint and Fork appear only when the machine's provider supports them. If a command is refused, the machine does not support that operation.

## Rename

cmux vm rename sets a display label, up to 64 printable characters. The generated name stays the machine's ID. Use --clear to remove the label.

```
cmux vm rename brave-otter "billing api"
cmux vm rename brave-otter --clear
```

## Status and stats

cmux vm status shows a machine's state, size, and address. cmux vm stats shows CPU, memory, and disk use without waking a paused machine.

```
cmux vm status brave-otter
cmux vm stats brave-otter
```

## Delete

Deleting a machine permanently deletes the machine and everything on its disk. It also removes the machine's public URLs and revokes its model access. You cannot undo a delete.

Make a checkpoint first if you think you need the files later.

```
cmux vm rm brave-otter
```

## When your plan ends

If your paid plan ends, machines older than 7 days are locked. You can still list, rename, and delete them, but you cannot open them, run commands, forward ports, or resume them. The machines and their files are kept. Upgrade again to reconnect. The Cloud sidebar shows Locked and an Upgrade to Reconnect menu item.

Canonical: https://cmux.com/docs/cloud/machines

Documentation index: https://cmux.com/llms.txt