Your machine
”Your machine is offline”
The chat input shows “<name> is offline” when the daemon on that chat’s machine isn’t connected.- Your own computer: make sure the desktop app is open, or that
reliant daemon startis running on that machine. Check withreliant daemon status, and read its log withreliant daemon logs. - A cloud machine: open Settings → Machines and look at its status. A Suspended machine has the Resume button; a failed one can be removed and recreated.
- Anything else: check that the computer has an internet connection and hasn’t gone to sleep. A laptop that sleeps drops its daemon, and it reconnects on its own when it wakes.
”Waking your machine…”
Cloud machines suspend after a period of inactivity (you can change the delay under Auto-suspend after inactivity in the machine’s settings, in Settings → Machines). Sending a message wakes one automatically, and the chat shows Waking <name>… until it’s ready. The chat shows Waiting for your machine… while it catches up. If a machine stays in Waking up… for many minutes, open Settings → Machines, check its status, and use Resume or suspend and resume it again. If it still won’t start, email support with the machine’s name. Suspended machines aren’t billed for compute, but their disk is, so the Machines page shows a small charge beside suspended machines. Delete a machine you no longer need to stop it.Tools work on the wrong computer
Each chat runs on one machine, and files, memories and MCP servers all live on that machine. A cloud machine has its own~/.reliant/ folder and its own copy of your repository, separate from your laptop’s. If something you set up “isn’t there”, check which machine the chat is using.
Signing in and your account
I can’t sign in, or I keep getting signed out
Try signing out and back in (Settings → Account → Sign out). If a provider login (below) expired, you only need to reconnect that provider; you don’t need to sign in to Reliant again.The desktop app won’t open or looks stuck
- Quit Reliant completely and open it again.
- Make sure you have the latest version (Reliant → Check for Updates), or reinstall from the download page. Your chats, projects and provider settings live in your account, so reinstalling doesn’t lose them.
- As a fallback, use the web app, which has the same features.
Models and providers
”Claude session expired. Please reconnect”
A provider login (Claude, Codex, Antigravity or GitHub Copilot) has expired, and the message names which one. Open Settings → AI → Your providers, choose the provider and sign in again.The login button doesn’t appear (web app)
Claude Code, Codex and Antigravity sign-in needs a small helper on your own computer. Runreliant auth serve in a terminal and leave it running; the button appears within a couple of seconds. See AI Providers. The desktop app doesn’t need this.
”Invalid API key”
Check that the key is complete, belongs to the right provider, and hasn’t been revoked. Test Connection in Settings → AI shows the provider’s own error.Rate limit or quota errors
These come from your model provider. When a provider’s usage limit is hit, the chat waits for the reset and continues by itself; it shows the reset time with Retry now and Stop, and offers another connected provider’s model when one can stand in. See AI Providers. If you use Reliant AI, an “account issue” message usually means your wallet balance is empty; add credit in Settings → Billing.A local model isn’t listed or won’t load
Local models (Ollama, LM Studio and others) are reached through a daemon on the machine that runs the model server. Check that the daemon is online (see above), that the model server is running, and that Settings → AI → Custom & local models lists it. If Ollama answers but the agent behaves badly, raise its Context length setting. See AI Providers.Responses are slow
Check your provider’s status page, try a smaller or faster model, and make sure you haven’t hit a rate limit. A machine that is still waking up also delays the first response.Billing
My run was blocked or won’t start
Runs that need a cloud machine or Reliant AI credit stop when there’s nothing to charge. Check Settings → Billing for an empty wallet or a failed payment, add credit or update your card, then resend the message.GitHub and projects
I can’t clone or open a pull request
Open Settings → GitHub. If it says the token expired or needs reconnecting, use Reconnect. Cloning a repository onto a cloud machine, and pushing from it, use that connection. On your own computer, pushes use the git credentials that computer already has. Opening a pull request uses the GitHub CLI (gh) on the chat’s machine, so install it and run gh auth login there. See Git Integration.
Workflows
A workflow seems stuck
- Check if it’s paused. Look for the pause indicator in the chat.
- Check the approval mode. In Manual mode, the workflow waits for you to approve each tool call.
- Stop and retry. Press
Escor click stop, then try a different approach. - Branch from earlier. Click the branch icon on any message to start fresh from that point.
A workflow fails repeatedly
Reliant pauses instead of crashing. Read the error message, fix the cause (a permission, the network, a provider limit), then resume.A chat is in a bad state
If an agent is confused or repeating errors, branch from an earlier message where things were working. Click the branch icon on any message.Logs
For a daemon on your own computer, the log is a single command away:reliant daemon ls lists them. For problems with the app itself rather than the daemon, mention what you were doing when you contact support. Cloud machine logs aren’t available on your computer; tell support the machine name and the time it happened.
Get help
Still stuck? Email support@reliantlabs.io with:- Your Reliant version (Settings → About)
- What you were trying to do
- What happened instead
- The machine involved (your computer or the cloud machine’s name)
- Any relevant output from
reliant daemon logs
See also: FAQ • Machines • Feedback & Support