Troubleshooting

Start with the failing surface and preserve the exact error. Atoi distinguishes four states:

• Configured: the required setting or connection exists.
• Degraded: the surface works partially or from cached state.
• Blocked: a named dependency prevents progress.
• Proven: the real user journey completed with current evidence.

Do not promote one state into another without proof.

#Sign-in does not complete

Confirm the browser can reach the Atoi login page and that cookies are permitted for the product domain. For the CLI, restart device authorization:

atoi account status --json
atoi account login

If an old CLI identity is no longer valid, sign out and authorize again:

atoi account logout
atoi account login

#A model is unavailable

Open Settings → Models and inspect the provider connection. A masked credential row proves that a value is stored, not that every model request succeeds. Try a supported model and preserve the provider error if it fails.

See Models and keys for BYOK setup and Provider matrix for the source-backed provider list.

#A connection cannot read or act

Open the Connection detail and inspect authorization, scope, and last error. Reconnect only when the provider grant is missing or revoked. A connected status does not imply permission to every object in the external service.

#A computer is offline

Open Computers and read the target status. Verify the companion or hosted target is connected before assigning work to it. Cached metadata is not proof that the target is reachable. See Computers.

#A task is waiting or failed

Open the task from its conversation or project. Look for an ask, an approval, a provider error, failed checks, or a disconnected computer. Resolve the specific boundary and retry from the existing task when supported; do not create duplicates just to clear the state.

#The CLI cannot connect

Run:

atoi status --json
atoi doctor --json

Then inspect account authorization with atoi account status --json. Use --help on the exact command when flags differ from an older example.

#Report a useful failure

Include the surface, route or command, exact error, expected action, current state, and whether the problem reproduces after a fresh sign-in. Never paste provider keys, session tokens, or unredacted credentials into a report.