Where to take a problem.
Pick by what kind of problem it is. Getting this right is the difference between an answer today and a thread nobody is watching.
Something is broken
Open an issue. The bug template asks for the component, your Node and Postgres versions and the agent version, because those three answer most reports on their own.
You have a question
Discussions, not issues. Setup questions, “is this supposed to work like this”, and anything where you are not yet sure it is a bug.
You found a vulnerability
Do not open a public issue. Use private vulnerability reporting on the repository, or email us. Acknowledgement within three working days.
Three things that fix most of it.
The agent shows offline
Run the agent’s status command. A 401 on the daemon connection means the machine’s API key is not registered on the server, not that the agent is misconfigured — re-enrol the machine from Settings → Machines.
Terminals connect but nothing happens
The reverse proxy is almost certainly not forwarding the WebSocket upgrade. The web app and the WebSocket server are two different ports and both need to be reachable.
A column is missing after a deploy
The migration script exists but was never added to the ordered list the deploy runs. That is a deliberate loud failure — add it and redeploy.
The mobile app.
The app is a client. It needs a Dialout server to talk to and an agent running on at least one machine — most app problems are really one of those two, which is why the answers below start there.
Sign-in fails on the phone but works in a browser
Check Settings → Server. A fresh install points at the hosted instance; if you self-host, that address has to be your own server, reachable over HTTPS with a valid certificate. A self-signed certificate will not connect.
The list of machines is empty
The account signed in has no machine enrolled, or every agent is offline. Enrol a machine from Settings → Machines on the web dashboard first, then pull to refresh.
A terminal opens but stays blank
The reverse proxy in front of your server is not forwarding the WebSocket upgrade. The API and the WebSocket server are two different ports and the phone needs both.
AI sessions show nothing
Sessions are read from the transcript each CLI writes, so the agent has to be version 2.7.2 or newer and the CLI has to have written at least one turn. An older agent reports no capabilities rather than failing loudly.
Face ID does not appear for a stored credential
Biometrics are checked by the operating system. If the device has no biometric enrolled it falls back to the passcode; if you denied the permission, re-enable it in the system settings for the app.
Alerts are switched on but nothing arrives
Push delivery needs the server side configured. Until then the toggle explains that push is disabled rather than pretending it works — deep links from a notification already work without it.
Need a response time in writing?
Community support is free and public. Paid support gives you a named contact and an SLA.