Skip to main content
Vibex reports failures as structured error codes, shown in the UI as error code: description. When you file an issue, include the complete error code string—it is more useful than the log body.

Remote and pairing

Sessions and workspaces

Files and content

Configuration and imports

Usage statistics

Releases and updates

Status values

These are not errors, but they are often misread:

General troubleshooting order

  1. Confirm the authoritative runtime is running and which one you are connected to (local embedded, or a remote server).
  2. Confirm the current project and workspace are correct—Local and Worktree are different directories.
  3. Confirm the device permission level is sufficient (write operations require full_control).
  4. Check the latest timeline event to see whether it is waiting on an approval or an elicitation form from you.
  5. If the problem persists, submit redacted information as described in Troubleshooting.