No models or a failed response test
- Confirm the selected provider, model, and active connection. A default provider with no selected model cannot run a request; a fresh project starts on Ollama with no model.
- For API/compatible endpoints, recheck the HTTPS or localhost-only endpoint, credentials, account limits, and model name. Reload the model catalogue. A slow endpoint may need a longer catalogue or test timeout in Request budgets and model capabilities.
- For a CLI, run its own sign-in/status check in a terminal, then Verify installation and Test response in Vopit. Check the executable selection: Codex CLI and Claude Code accept their .exe or standard npm .cmd shim on Windows, while Mistral Vibe, Mammouth Code and Antigravity CLI need their native executable (vibe-acp, mammouth).
- Claude Code reports that the selected model is unavailable: check the model name, or leave the agent's model blank so it uses the connection's model. Base team agents follow the workspace default connection unless you give them their own model.
- If a stream disconnects, see a rate, token, or endpoint error, correct the provider-side cause before retrying. Confirm success with a bounded test request.
A request is blocked, partial, or failed
Open the selected request and inspect its ticket, activity, error, permissions, model settings, and changed files. Make an intentional choice: Resume keeps recovered state; Restart and Edit and restart create a new request. Resolve denied paths, missing coordinator/executor configuration, timeout/turn limits, review exhaustion, or provider failures before retrying.
A partial request marked “Almost there · open points remain.” finished its work while some blockers stayed unresolved. Read its Open points, fix any missing access or configuration they name, then choose Fix open points: the team handles only those points in a new request, and existing files stay in place. A partial request whose review budget ran out instead offers Resume request, which continues the pending corrections. If correction rounds or Git stages did not run at all, check the header speed mode: Ultra-fast skips them and Balanced allows at most one correction round.
Infrastructure operation or upload fails
- Fingerprint, authentication, key-format, or passphrase failure: verify the endpoint independently and import the original compatible private key.
- Operation unavailable: verify the connection is Enabled, granted to the agent, saved, and that the operation's policy is Confirm each execution or Allow for assigned agents rather than Disabled.
- Upload failure: check that the file is no larger than the SSH target’s configured limit (1,024 MiB by default; 1–65,536 MiB), local READ permission, a relative remote path, and an existing parent inside the configured root. Project packaging scripts can impose a separate archive limit. Check your project’s packaging requirements independently.
- Deployment succeeds but the application is unavailable: run the configured health operation, inspect the logs and routing for the actual stack, then use the reviewed rollback if necessary. Container, service, cluster and static-hosting checks differ; see Deployment patterns.
| Target | Useful diagnostic evidence |
|---|---|
| Application service | Configured service status, application logs and a known health response. |
| Container project | Container state, application health checks and the exact image digest. |
| Cluster | Authorized namespace, rollout state, readiness and public routing. |
| Static hosting | Published asset manifest, cache state and expected public paths. |
| Database | Connection/TLS result, migration version and a bounded query result. |
Installation, sign-in, or license failure
- Check Downloads for an available release for your platform. If none is listed, that platform does not currently have a published installer.
- If desktop sign-in remains pending, complete the browser flow on the same computer. Cancel and retry the app sign-in if the callback window has expired or was closed.
- For an inactive or expired license, ask a Vopit administrator to review the account’s license and expiry, then choose Check license in the app.
- If a password changed, sign in again; existing sessions are revoked. If access still fails, contact the person managing your license and report the message shown in the app.
Collect useful diagnostics without exposing data
- Record the request status, failed ticket, provider/model, operation label, and actual error. Export the selected session when necessary.
- Open Settings → Advanced → Structured logs → Export to save real event and tool-result records. Reveal beside SQLite database opens its location; it is not an import or recovery wizard.
- Use Debug mode only when longer tool excerpts are needed. Review exported files for project content and sensitive output before sharing them.
- Preserve the failing evidence, correct the configuration, and run one bounded verification task. Keep database backups separate from JSON diagnostic exports.
Git Manager cannot prepare or finalize
- A project without a repository is initialized by git_prepare after GIT_WRITE approval, on git.baseBranch. Without Git on the computer, Git Manager stages are skipped and the request runs without a branch or commit; install Git from git-scm.com, no restart needed. Git with no user.name or user.email commits as Vopit <vopit@localhost> until you configure your own. A project folder inside a parent repository is refused: open the Git repository root instead.
- Existing staging is preserved and can block preparation/finalization. Review and resolve it yourself. Initial dirty files are excluded from the request commit, even if an agent edits them later.
- A repository with no commit cannot materialize several main branches yet. Eligible new request changes must produce the first commit; pre-existing untracked files are not automatically included.
- A branch/file change during approval or independently changed staging during commit recovery blocks the operation. Inspect Git status before Resume; recovery does not discard your work.
- Remote/history action denied: enable its project switch, grant the Git action, review the relevant permission and configure authentication locally. Merge/rebase also require an explicit branch.
- A request waits instead of running in its own worktree: uncommitted files in the project folder would be missing from a separate worktree, and a repository without a commit cannot run requests in parallel. Commit the project once, or let the request wait; Vopit tries a worktree again every 60 seconds. Linked folders, a branch already prepared in the project folder, or Run requests in parallel switched off also make it wait.
- A linked folder could not be committed: the project and other repositories keep their commits, and the failure is listed as an open point with the result. Resolve it in that repository, then use Fix open points or commit it yourself.