> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reliantlabs.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Start, stop and resize cloud machines from the CLI

> Control your Reliant cloud dev environment from a terminal: list machines, stop one to save hours, resize it while suspended, start it, and rename it.

By the end of this guide you can manage your Reliant cloud machines from a terminal: stop a machine so it stops using hours, change its size, start it again and rename it. `reliant machine` calls the same API as **Settings → Machines**, so a change in one shows up in the other.

## Before you begin

* A cloud machine, created in **Settings → Machines** under a compute plan ([Cloud machines & plans](https://docs.reliantlabs.io/machines/cloud.md)). The CLI cannot create or delete machines.
* The `reliant` CLI on any computer ([Installation](https://docs.reliantlabs.io/getting-started/installation.md)). Run `reliant --version` to check.
* A login made with `reliant auth login` by the release you run. Only that login has the `daemon:manage` permission, and only a person's login can hold it.

**1. Sign in with a login that can manage machines**

```bash terminal theme={null}
reliant auth login
```

Any other credential is refused, including a deploy token or a login from an older release. This is what you see with a token that lacks `daemon:manage`:

```text terminal theme={null}
$ reliant machine list
unauthenticated: missing owner in context
  hint: managing machines needs a login made by this release: run 'reliant auth login'
```

**2. List your machines**

```bash terminal theme={null}
reliant machine list
```

The output is a table with the columns `NAME`, `ID`, `TYPE`, `STATUS` and `SIZE`. `TYPE` is `managed` for a cloud machine and `connected` for a computer you connected yourself. `STATUS` is `active`, `suspended`, `pending`, `disconnected` or `failed`. Every other verb takes a machine's name or its id. When two machines share a name, pass the id.

**3. Stop a machine**

Stopping suspends the machine. Its compute is released and it stops using hours. The disk is kept, so your checkout, installed tools and uncommitted files are still there when it starts again. Running processes, such as a dev server, are not kept.

```bash terminal theme={null}
reliant machine stop my-box
```

It prints `Stopping my-box (<id>).` and returns without waiting. Run `reliant machine list` until `STATUS` shows `suspended`.

**4. Resize it while it is suspended**

The sizes are `s1`, `s2`, `m`, `l`, `xl`, `2xl` and `3xl`, smallest first ([Machines overview](https://docs.reliantlabs.io/machines/overview.md)). Your plan decides the largest one you can pick.

```bash terminal theme={null}
reliant machine resize my-box l
```

It prints `my-box (<id>) is now l; it takes effect when it next starts.` A running machine is refused with `hint: stop it first: reliant machine stop my-box`, so the order is always stop, resize, start. A size your plan does not allow is refused here, with the same answer a start would give. Disks only grow: moving to a smaller size keeps the larger disk.

**5. Start it**

```bash terminal theme={null}
reliant machine start my-box
```

It prints `Starting my-box (<id>). It takes a minute or so to come up.` If the machine is not suspended, you get `machine my-box is not suspended`.

**6. Rename it**

A name is only a label. The machine's id and workspace stay the same, so chats, automations and links that point at it keep working. A name is 1–63 lowercase letters, digits or hyphens, starts and ends with a letter or digit, and must be unique among your machines.

```bash terminal theme={null}
reliant machine rename my-box api-box
```

It prints `Renamed my-box to api-box (<id>).` Rename works on any of your machines, cloud or connected, running or not.

**7. Check the result**

```bash terminal theme={null}
reliant machine list
```

The row should show the new name, `STATUS` `active` once the machine is back up, and the new size in `SIZE`. **Settings → Machines** shows the same values.

## What wakes a machine

You often do not need `start` at all. A suspended machine is woken by:

* a run's preflight, when a chat or [automation](https://docs.reliantlabs.io/automations/overview.md) starts work that needs it;
* a message you send in a chat on it;
* opening the Files tab or a worktree operation in the app, which shows "Waking up…" and retries.

An agent's tool calls in the middle of a run never wake a machine. After the idle timeout you chose when you created the machine, it suspends itself ([Waking and suspending](https://docs.reliantlabs.io/machines/cloud.md#waking-and-suspending)). For what happens to a run while its machine is away, see [how a tool call reaches your machine](https://docs.reliantlabs.io/deep-dives/how-tool-calls-reach-your-machine.md).

## What this does not do

* **It does not create, delete or grow disks.** Do those in **Settings → Machines**. **Grow disk** is limited by your plan's storage cap, and a disk cannot be made smaller again.
* **It does not run from an agent's shell.** `start`, `stop` and `resize` refuse inside an agent's shell, with `an agent cannot start, stop or resize machines from its shell`. An agent uses its `manage_machine` tool instead: `start` and `resize` show you an approval card in the chat first, and `stop` never stops the machine the agent's own run is on.
* **It does not keep processes across a stop.** Only files on disk survive a suspend.

## Troubleshooting

> [accordion] unauthenticated: missing owner in context
>
> The CLI is not signed in with a login that has `daemon:manage`. Run `reliant auth login` with the release you are using. `reliant auth status` can still say "Logged in" for a credential without that permission.

> [accordion] no machine "…": 'reliant machine list' shows yours
>
> No machine of yours has that name or id. The name must match exactly, and it changes when you rename a machine.

> [accordion] 2 machines are named "…": pass the id instead
>
> Two of your machines share the name. Use the `ID` column from `reliant machine list`.

## Next steps

> [card] [Share a dev server from a machine](https://docs.reliantlabs.io/guides/machines/share-dev-server-preview-url.md)
>
> Get a preview URL for a port and decide who can open it.

> [card] [Cloud machines & plans](https://docs.reliantlabs.io/machines/cloud.md)
>
> Sizes, included hours, idle timeouts and disk billing.

> [card] [Troubleshoot an offline machine](https://docs.reliantlabs.io/guides/machines/troubleshoot-offline-machine.md)
>
> When a chat says your machine is offline or waking.

> [card] [CLI reference: reliant machine](https://docs.reliantlabs.io/reference/cli.md#reliant-machine)
>
> Every flag of every verb.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.