Troubleshooting
“Startup didn’t complete”
Section titled ““Startup didn’t complete””The app opened but reports that the Pavii Engine couldn’t finish starting.
- Restart the app first — transient startup races resolve themselves.
- If it repeats, use the Send diagnostics button on the error dialog; it attaches the startup logs we need.
- A rare cause is a data directory written by a newer app version than the one now running (for example after rolling back an update) — the engine refuses to open newer data rather than risk corrupting it. Updating the app resolves it.
Stuck on the sign-in screen
Section titled “Stuck on the sign-in screen”The app waits for your browser to hand back a session. If it keeps waiting:
- Make sure you completed the login in the browser window that opened.
- If you signed in using a different browser or profile, the handover cannot reach the app. Use copy the sign-in link on the welcome screen and open it in the browser the app launched.
- Some browsers ask for permission before handing a link back to a desktop app. Allow it if prompted.
An agent shows as missing
Section titled “An agent shows as missing”- OpenCode ships inside the installer and should always be available. If you installed your own copy and later removed it, restart the app so detection re-runs.
- Claude Code / Codex / Gemini CLI are detected from your system PATH. After installing one, restart Pavii.Ai so the engine’s agent detection sees it.
The ”/” menu shows no agent commands
Section titled “The ”/” menu shows no agent commands”Agent commands come from the connected CLI. They appear once the agent has started in a conversation, and they persist between turns afterwards. App commands and skills are available immediately regardless.
A team member is stuck
Section titled “A team member is stuck”Team members show their own state, and most of them are not errors:
- Starting - the runtime is warming up; sending is briefly blocked.
- Failed to start - retry that member’s runtime from its controls; the rest of the team keeps working.
- Session stopped - the member was reclaimed while idle. Sending a message restarts it automatically.
- Idle - normal between turns. Members finish a turn and wait to be woken rather than holding a connection open.
If a member seems to hang mid-task, interrupt it from the member controls (or ask the lead to) rather than waiting - a turn held open too long is eventually failed by the model provider.
Agents keep disappearing from memory
Section titled “Agents keep disappearing from memory”There is an agent idle timeout in settings that shuts down idle agent processes to free memory. If you would rather agents stay resident between bursts of work, raise it.
The window renders oddly or the app is sluggish
Section titled “The window renders oddly or the app is sluggish”Hardware acceleration can be turned off in settings. The app also disables it automatically after repeated GPU crashes, so if you find it already off, that is why.
Where things live
Section titled “Where things live”- Conversations and settings — the app’s local data directory.
- Logs — collected automatically by Send diagnostics; the in-app bug report (Settings → About → Report Issue) attaches recent logs as well.
Updates
Section titled “Updates”Updates download in the background and apply on restart. The About page shows the current version and a manual Check for updates button.