Troubleshoot a task
Find which stage failed before retrying: connection, model request, tool access, execution, or result verification. Keep the existing result and error available while you diagnose it.
The model is unavailable
- Check the selected provider/model and its actual sign-in or service state. For a local model, check that the server is running and the model is loaded.
- Inspect quota, rate-limit, and authentication errors. A different model or account should be selected explicitly.
- Recheck the connection, then use a small read-only request. Save the exact error if it fails again.
agentlas doctor
agentlas help doctorA tool or browser is unavailable
Check installation, connection, local credentials, granted permissions, and the intended browser account. A catalog listing or agent requirement does not establish readiness. Reconnect the missing component, then test a single read.
A run stopped or appears stuck
Open its run status and history. Check whether it is waiting for input, permission, a provider, or an execution host. Preserve partial artifacts. Use the visible stop/cancel action when you intend to stop, and confirm the terminal state before starting another copy.
Sending or publishing has an uncertain result
Inspect the destination and run receipt before repeating the action. If a message, upload, purchase, or publish may already have happened, reconcile that state first to avoid duplicates. Report what is confirmed and what is still unknown.
A task says done but the output is missing
Open the requested file, folder, or external result. Compare it with the requested format and acceptance criteria. A final chat message, a generated plan, or a success badge cannot replace the artifact itself.
Your phone cannot reach Desktop
Keep the paired Desktop host running. Check account, selected device, network, and supported versions. If pairing expired, create a fresh QR code. Notification registration and delivery are separate from pairing.