Skip to main content
By the end of this guide a workflow runs where you tell it: the whole thing on one machine, and any step on a different one. Use it to run a slow test suite on an always-on server while you work on your laptop, or to send one step to a machine with a GPU. A workflow, or any node in it, takes a daemon: field. When a run has to choose, the most specific instruction wins: the node’s daemon:, then the workflow’s, then the machine the chat or automation runs on, then your default machine (choosing a machine in workflows).

Before you begin

1

Find each machine's name and kind

Open Settings → Machines. A daemon: can name a machine by its name, its hostname or its id. Each machine is also one of two kinds:
  • local: a daemon you run yourself, on a laptop, a workstation or a server you own.
  • cloud: a Reliant cloud machine.
The kind follows who runs the daemon, not where the computer is: a rented server running reliant daemon start is local.
2

Send the whole workflow to one machine

A top-level daemon: applies to every node. Here every step runs on the server named build-box:
.reliant/workflows/nightly-suite.yaml
local, cloud and any are kinds. Any other string is a machine’s name, hostname or id.
3

Send one step somewhere else

A node’s own daemon: overrides the workflow’s. Add a benchmark step that runs on a connected cloud machine labelled gpu=true, and a message for when the suite fails:
.reliant/workflows/nightly-suite.yaml
A selector can hold id, name, type and labels, and every field you give must match. On a run node, daemon: decides where the command runs; on an agent node, where that agent’s tools run. The value can also be a CEL expression such as "{{ inputs.where }}".
Labelling a machine (reliant daemon start --label, reliant machine label) needs reliant v1.23.0 or later; check with reliant --version. Labels are checked only against connected machines. When none of them matches, the step can fall back to a machine that matches the selector’s other fields, so give a type or name you would accept.
4

Validate the workflow

terminal
terminal
Validation checks the selector’s shape. A misspelled field fails with unknown daemon selector field: "label". It can’t check that build-box exists, so a wrong name only shows when the run reaches the step.
5

Check where each step ran

Run a workflow whose steps record their hostname. Replace build-box with your machine’s name; the node uses the selector form to show that every field must match:
.reliant/workflows/where-it-runs.yaml
--daemon sets the run’s own machine, the level below the workflow’s daemon::
terminal
terminal
The same run with type: cloud failed the step, because that machine is local (see Troubleshooting).

What this does not do

  • It doesn’t move your files. Each machine has its own copy of the project. A step on another machine runs in that machine’s checkout, so it sees what was pushed and pulled there, not uncommitted edits from the chat’s machine. A machine without the project fails the step with <project> isn't checked out on <machine>.
  • It doesn’t follow a branched chat’s workspace. That workspace exists only on the machine that created it. A node that names another machine doesn’t see it.
  • It can’t run without a machine. A workflow with a daemon: anywhere can’t be a no-machine run.
  • It doesn’t check a node’s machine up front. A run waits for its workflow-level machine when it starts, and wakes it if it is a suspended cloud machine. A node’s own machine gets no such check: a run step whose machine is offline waits up to 30 minutes for it to connect, then fails.

Troubleshooting

The step’s selector matched none of your connected machines. The step fails with this run's machine no longer exists; the command never ran, even though nothing was removed. Check the spelling of the name, and that type matches the machine’s kind: a server you run the daemon on is local.
A selector holds only id, name, type and labels. Fix the field name and validate again.
--project-path created the project a moment ago, and its machine hasn’t sent the project’s workflows to Reliant yet. Wait a minute and run the command again.
The step’s machine is a suspended cloud machine. Send a message in the chat, or click Resume in Settings → Machines.

Next steps

Choosing a machine in workflows

The resolution order, automations, and machine status.

Fix an offline machine

When the machine a step needs isn’t connected.

Run the daemon on your own server

An always-on machine to pin long jobs to.

How a tool call reaches your machine

What happens between the run and the machine.