reliant daemon status reports that stream, not just whether a process exists, so it tells you which link is broken (how a tool call reaches your machine).
Before you begin
- The name of the chat’s machine. The chat shows it, and Settings → Machines lists all of yours.
- For your own computer or server: a terminal on it, and the
reliantCLI (Installation).
Read what the chat says
On a cloud machine, check Settings → Machines
On your own computer, check the daemon's stream
--workspace <path>):status exits 0 only when the stream is established and has held for two minutes. With no daemon running:reliant daemon start (connect your computer). A daemon that runs but has no credential says so:reliant daemon ls lists every instance on the computer with its stream state:Read the daemon's log
reliant daemon logs shows the last 50 lines and follows, but reads only the last 1 MB. For anything older, search the file itself, logs/tools-daemon.log beside the record status printed:Session ended; reconnecting and Gateway stream is dead are drops the daemon recovers from by itself. Rejected: credentials not accepted — retrying, repeated, usually means the credential was revoked or the machine removed: go to the next step. Fatal error — not reconnecting means the daemon stopped, and the line says why.Re-register a daemon whose credential is refused
daemon start prints a pairing code to approve in the app. On a server with no browser, give it a new token with --token instead (run the daemon on your own server).Check that the machine is back and the run resumed
reliant daemon status again. It now starts with Daemon is running and its gateway stream is established and exits 0, and the machine shows as connected in Settings → Machines.A paused chat resumes on its own when its machine connects. To retry sooner, send a message in the chat, or resume a run from the CLI with reliant workflow resume <execution-id>.What this does not do
- Tool calls are not queued for an absent machine. A call made after the daemon has been gone for 90 seconds fails at once.
- A crash takes up to 90 seconds to show. A clean
daemon stopshows as disconnected immediately; a crashed daemon looks connected until 90 seconds pass without a heartbeat. - Tool calls don’t wake a cloud machine. Sending a message, or the check a run makes when it starts, wakes it.
Troubleshooting
no daemon connected for user
no daemon connected for user
the machine this request asked for is not connected
the machine this request asked for is not connected
daemon: names a machine that isn’t connected, or that matches none of yours. Check the name and the kind in the workflow (choose which machine runs each step).Your machine didn't come online within …
Your machine didn't come online within …
Your message is queued and will be sent as soon as your machine connects, so start the machine and the message is delivered.refusing to start: daemon PID … already runs in data directory …
refusing to start: daemon PID … already runs in data directory …
reliant daemon stop first. To run a second daemon on purpose, give it its own --data-dir.another daemon process claimed this daemon's identity …
another daemon process claimed this daemon's identity …
reliant daemon ls, stop the copy you don’t want, and keep one.daemon gateway stream is flapping — …
daemon gateway stream is flapping — …
Session ended; reconnecting lines and their errors. A network that blocks long-lived HTTPS connections to gateway.reliantapi.com causes this.Next steps
How a tool call reaches your machine
Choose which machine runs each step
daemon:.