Skip to main content
Most of Reliant happens in the app: you chat, pick a machine, review changes. The reliant command line tool covers the jobs that belong in a terminal. It turns a computer you own into a machine your agents can work on. It signs you in where there is no app, such as an SSH session or a CI runner. It lets you build and test workflows next to the code they live with, and start or supervise runs from scripts. It also ships Forge, so reliant forge … builds and deploys your apps signed in as you. This section is organised by job rather than by command. Each page follows one job from start to finish, with real output. For every command and flag, see the generated CLI reference.

​
Getting the CLI

The desktop app installs reliant and puts it on your PATH; Installation covers each platform. On a Reliant cloud machine it is already there. To check which build you have, and which Forge it carries:
The forge: line matters more than it looks: reliant forge runs exactly that Forge version, as Forge through Reliant explains.

​
Which server, which credential

Every command that talks to Reliant first decides where to talk and as whom. The CLI keeps no “current server” setting that a previous command could leave behind. It works the server out again on every run, in this order:
  1. the --server flag,
  2. the RELIANT_SERVER_URL environment variable,
  3. the default compiled into the binary, which is Reliant’s hosted service (https://api.reliantapi.com).
You almost never set either of the first two. They exist for people running their own Reliant stack. The credential comes from the RELIANT_TOKEN environment variable if it is set, and otherwise from the login stored for that server. A login made against one server is never sent to another. When a command fails, the error names both the server and where that choice came from, which tells you straight away whether the problem is the credential or the target:
Daemons are the exception. A daemon authenticates with its own credential, made when you register the machine, so signing the CLI out does not disconnect a running daemon. Sign in and tokens explains the three kinds of credential and when to use each.

​
Where the CLI keeps things

You rarely need to open these files. reliant auth status and reliant daemon status print the path they read, so you can see which file a command used.

​
Shell completion

reliant completion bash|zsh|fish|powershell prints a completion script. reliant completion <shell> --help explains where to put it for your shell.