Skip to main content
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). The CLI cannot create or delete machines.
  • The reliant CLI on any computer (Installation). 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

terminal
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:
terminal
2

List your machines

terminal
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.
terminal
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). Your plan decides the largest one you can pick.
terminal
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

terminal
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.
terminal
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

terminal
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 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). For what happens to a run while its machine is away, see how a tool call reaches your machine.

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

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.
No machine of yours has that name or id. The name must match exactly, and it changes when you rename a machine.
Two of your machines share the name. Use the ID column from reliant machine list.

Next steps

Share a dev server from a machine

Get a preview URL for a port and decide who can open it.

Cloud machines & plans

Sizes, included hours, idle timeouts and disk billing.

Troubleshoot an offline machine

When a chat says your machine is offline or waking.

CLI reference: reliant machine

Every flag of every verb.