Start with the message or status visible in Desktop. Each symptom points to a different check, while restarting everything at once can hide the original problem.
| Symptom | Check first | Safe next action |
|---|---|---|
| Provider required or credential required | Selected provider, API key, or local endpoint | Complete provider setup and run a short test |
| Runtime never becomes ready | Desktop diagnostics and Local Core status | Preserve logs, then restart Local Core from the supported control |
| Managed database is unhealthy | Database status in diagnostics | Use the documented database recovery action; do not delete application data |
| Workspace is missing | Folder exists and Desktop still has permission | Re-add the folder through the project picker |
| Session will not continue | Last terminal status and waiting reason | Use operator control or recovery on the same session |
Confirm the fix
Return to the original workspace and session, then run a small request. A recovery is complete only when the affected status clears and the existing history remains usable.
If the symptom persists, capture the visible status, Desktop version, platform, and the smallest repeatable sequence before reporting an issue.