Troubleshooting

Find the case that matches what failed and follow it to a fix. Start from the app that failed, keep the exact error text, and work through one cause at a time.

#Sign-in does not complete

Make sure the browser can reach atoi.app and allows cookies for it. In the terminal, restart device authorization:

atoi account status --json
atoi account login

If an old terminal identity is stale, sign out and back in:

atoi account logout
atoi account login

#A model is unavailable

Open Settings → Models and look at the provider. A saved key shows only that the key is stored, not that every request succeeds. Try another enabled model. If it still fails, keep the provider's error message. It usually names the cause: a balance, a region, or a retired model.

A failed request stays on the message with a Resume action. Fix the cause, then resume instead of sending again. If Atoi answered with a different model than the one you picked, the message says which model ran.

See Models and keys and Providers.

#A connection cannot read or act

Open Settings → Plugins (that tab holds your Connections), then open the Connection. Check its scope and the last error. Reconnect only if the grant is missing or revoked. A connected badge does not mean access to every repository, board, or document. See Connections.

#A computer is offline

Open Settings → Computers and read the status. A computer that was connected earlier can be asleep or disconnected now. Reconnect it before assigning work. See Computers.

#A task is waiting or failed

Open the task from its thread or from the panel's Tasks tab. Look for an ask, an approval, a provider error, a failed check, or a disconnected computer. Resolve that one thing and continue the same task. Do not start a duplicate to clear the state.

#The terminal cannot connect

atoi status --json
atoi doctor --json
atoi account status --json

Read the three results separately. They tell you whether the binary runs, the backend answers, and the account is authorized. When a flag looks different from an older example, atoi <command> --help is the truth.

#Write a report that gets fixed

Never paste keys, session tokens, or unredacted credentials into a report or a thread.

Include the surface, the route or command, the exact error, what you expected, what state you were in, and whether it happens again after a fresh sign-in.

Read FAQ and glossary when the word you do not recognize is the part that is confusing.