Before you begin
- A Linux server, x86_64 or 64-bit ARM. On a Raspberry Pi, that means a 64-bit OS:
uname -mmust printaarch64. There is no 32-bit ARM build. - The
reliantCLI on the server. The Linux.debpackage puts it at/usr/bin/reliant(Installation). - A git repository on the server for agents to work in, for example
~/src/my-service. - systemd. The daemon runs in the foreground and never detaches itself, so a service manager keeps it up.
1
Create a daemon token in the app
In the app, open Settings → Access tokens, click New token, name it after the server and click Create. Copy the
rlat_… token: it is shown once.This must be a token from that page. A token from reliant auth token create acts on the API as you, but it cannot connect a daemon, and the gateway refuses it (see Troubleshooting).2
Give the token to the daemon once
On the server, from the repository, start the daemon with The daemon asks Reliant which account the token belongs to, saves it to When
--token and paste the token at the prompt. --name is the name the app shows.terminal
terminal
~/.reliant/daemon.json and connects. Anything that is not an rlat_ token is refused before anything is saved:terminal
reliant daemon status in a second terminal reports the stream as established, stop this daemon with Ctrl+C. Later starts reuse the saved token.3
Run it as a systemd user service
Create the unit file.
WorkingDirectory picks the repository the daemon serves.~/.config/systemd/user/reliant-daemon.service
--non-interactive stops a restart from waiting on a pairing code nobody will see. If the credential is ever missing, the daemon stays up and waits for one to appear on disk. Use the path command -v reliant prints in ExecStart.terminal
enable-linger keeps your user services running after you log out and starts them at boot.4
Verify it is connected
From the repository, A connected daemon starts with The machine also appears under Settings → Machines. Start a chat on it and ask the agent to run
reliant daemon status exits 0 only when the stream to Reliant is established and stable:terminal
Daemon is running and its gateway stream is established. If the token did not get saved, you see this instead, with exit code 1:terminal
uname -m.5
Read its logs
terminal
daemon logs reads the end of the daemon’s log, tools-daemon.log, in its instance folder under ~/.reliant/instances/. It only looks at the last 1 MB, so grep that file for older history. reliant daemon ls lists every daemon instance on the server.6
Stop or remove the machine
Stop the service, not the daemon: systemd would start a daemon you stopped by hand again.To retire the server for good, also revoke its token under Settings → Access tokens and run
terminal
reliant auth logout on the server to delete the saved credential. Then choose Forget This Machine under Settings → Machines. Forgetting removes only the connection record: a machine that reconnects reappears.What this does not do
- No 32-bit ARM. Release builds are for 64-bit Linux, macOS and Windows on x86_64 and ARM64.
- No sandbox by default. The daemon runs as the user that owns the service, and an agent’s commands can read whatever that user can. Run it as a dedicated user, and see the daemon security model for what
credentials: nonehides. - No inbound port, and no reach into your network beyond what the server has. The daemon dials out; agents reach only what the server itself can reach (how a tool call reaches your machine).
Troubleshooting
token rejected by gateway … (unauthenticated)
token rejected by gateway … (unauthenticated)
The gateway refused the token, and nothing was saved. You get this when the token was revoked, or when it is not a daemon token. A Create a token under Settings → Access tokens and run step 2 again.
reliant auth token create token gives exactly this:terminal
awaiting_credentials
awaiting_credentials
The service started before a credential was saved, or
reliant auth logout removed it. Stop the service (systemctl --user stop reliant-daemon), run step 2 as the same user from the same repository, then start the service again.The service stops when you log out
The service stops when you log out
Run
loginctl enable-linger "$USER". Without it, systemd stops your user services when your last session ends.Next steps
Connect your computer
Pair a machine with a code you approve in the app.
Pin a workflow to a machine
Send a workflow’s runs to this server.
Troubleshoot an offline machine
When a chat says the machine is offline.
Run a machine from the terminal
Every status field, stop’s rules, and several daemons on one computer.