Troubleshooting
Diagnose connection, activation, project, preview and recovery problems.
On this page
Start with the least destructive step
Save your project and keep a backup. Record the installed version, operating system, the action that failed and the safe error or run identifier. Restore the existing conversation before creating another modifying run. Do not clear history, reinstall everything or delete project folders as a first response.
Connecting AI workspace or service unavailable
Check the project name and /status. Confirm you have an internet connection and can open your account. Wait for the workspace connection before sending another task; use Retry if offered.
If the account works but the Agent does not, capture the service error and run identifier. A backend outage is not solved by entering an API key into chat. Keep working manually if the editor is usable, and contact product support.
Model unavailable or authentication failed
Open /model and inspect the access mode and availability. Managed access needs an active entitlement; BYOK needs a valid saved provider key, provider credit and access to the requested model. Use the native credential dialog to correct a key. Do not assume a different thinking level can fix authentication.
If a code is rejected, distinguish website sign-in from desktop activation. See account recovery. Avoid repeated rapid requests, which can trigger rate limiting.
Missing symbols, footprints or files
Confirm the project was extracted fully and opened from a writable folder. Repair local library paths and keep .pretty folders with the project. Refer to Projects and libraries. Do not substitute arbitrary symbols or footprints merely to make an error disappear.
Run appears stuck or duplicated
Expand the latest tool event. A long-running tool and a disconnected display are different problems. Use Stop if you no longer want the operation, then wait for a terminal status. Reopen the same conversation and inspect candidate state before retrying. A timeout does not prove the original operation never happened.
If the UI shows an invalid lifecycle transition, retain the error and run identifier. Do not overwrite candidate files or manually change stored run state. Support can use the identifier to trace the failed transition.
Plan, preview or review fails
Reopen the Plan handoff and confirm the revision. Unanswered questions, failed checks, missing tools and stale project context can prevent the next action. A large preview may be unavailable even though the candidate file exists; inspect the exact native artifact and preserve the error.
If approval expired or the trusted project changed, obtain a fresh review. Never bypass the conflict by copying candidate files over your project. See review and recovery.
Send a useful report
Include: version, OS, steps, expected result, actual result, safe error/run identifier and whether the trusted project changed. Screenshots are helpful after checking them for private names, keys, codes and project contents.
Use Support and select the correct category. The form returns a reference only after accepting the request. If submission times out, retain your draft and check for confirmation before resubmitting. Do not send an entire confidential project unless you explicitly agree to a secure support exchange.