Troubleshooting runners.
The common failure modes and what they mean.
The installer says Python 3.13+ is required
Install Python from python.org (on Windows, tick "Add to PATH") and re-run the one-line install.
ordel is not recognized, or ordel: command not found
On Windows, open a new terminal window: the installer adds ordel to your
PATH, but terminals that were already open do not see it yet.
On macOS and Linux, the ordel command is symlinked into ~/.local/bin.
Add that folder to your PATH, or call the binary directly:
~/.ordel/venv/bin/ordel.
A session on my runner opens no browser and shows Disconnected
Almost always the reachability rule: the target URL is not resolvable from
your machine (for example an internal cloud hostname). Re-check the
application's URL from the runner's machine, if curl <url> fails
there, the session cannot work there.
A run failed with no error details
Known limitation being fixed: failures executed on a runner can currently arrive without the underlying error text. Re-run the same script in the cloud to see the full failure, or check the terminal where the runner runs.
The runner shows as offline
Run ordel-runner start.
The one-line install sets the runner to start automatically each time you sign
in; if you started it by hand in a terminal instead, it stops when that
terminal closes.
Re-running the one-line install is safe and restores the automatic start.
Start over completely
ordel-runner uninstall
rm -rf ~/.ordel/venv ~/.local/bin/ordel-runner
curl -fsSL https://ordel.io/api/agent/install.sh | sh
On Windows, re-run irm https://ordel.io/api/agent/install.ps1 | iex; it
rebuilds the runner's environment from scratch.