Skip to main content
Vibex is local-first: the authoritative runtime stores projects, workspaces, sessions, timelines, provider profiles, terminal metadata, and remote device records. Remote connections receive only authorized projections.

​
Where data lives

Relay rooms and connections are ephemeral. Relay logs should contain only routing, counts, and timing metadata.

​
What survives a restart

When you restart the authoritative runtime, it reloads workspaces, sessions, and configuration from persisted records. The key distinction: Kept (written to SQLite):
  • Projects, workspaces, and workspace modes
  • Sessions, timeline events, and messages
  • Provider profiles, MCP servers, and Skills
  • Terminal metadata (tab names and bindings)
  • Remote device authorizations
Not kept (in memory only):
  • Running Agent processes
  • Terminal session contents and scrollback buffers
  • Active connections and live event subscriptions
A running value in the database is only the last observed state; it does not mean the process is still running. If you see a session marked running after a restart, confirm whether the process actually exists before you decide to retry.
Lost terminals are marked stale. Trust the new terminal snapshot and do not repeat commands based on an old one.

​
Device revocation

After you revoke a device in the authoritative runtime’s device list, that device’s active connections immediately receive device_revoked and close.
  • Using it again requires re-pairing.
  • The old QR code, connection string, authorization, and ticket are all invalid and must not be reused.
  • The revocation is written to the device audit record.

​
Diagnostic data

Settings → Data & Diagnostics provides the diagnostic export entry point. Before exporting, verify the redaction: Must be removed:
  • Tokens, private keys, pairing codes, and connection strings
  • Full prompts and file contents
  • Git diffs and raw terminal bytes
Safe to keep:
  • Version, release channel, and platform
  • Structured error codes
  • Redacted timestamps
  • Non-sensitive resource ids
A diagnostic export is one-way: once you post it to a public channel, you cannot take it back. Read it yourself after exporting before you decide to upload it.

​
Backup

  • Shut down the authoritative runtime before backing up SQLite, or use the safe backup procedure the project provides.
  • After restoring, check that workspace paths, device authorizations, and provider credential references are still valid.
  • Headless runtime data lives in /data by default; mount it as a persistent volume so sessions survive a container rebuild.

​
Cleaning up data

Settings → Data & Diagnostics lets you clean up local storage by category: sessions and attachments, terminal data, and diagnostic data. These operations cannot be rolled back.
Resetting settings only affects preferences; deleting the database, the data directory, or a workspace directory are different destructive operations. Before you run any of them, make sure you really no longer need that data.

​
External service boundaries

Agents and MCP servers may send context you explicitly provide to providers or external services. Read the privacy policy of each service before you use it, and control the data range with the smallest scope, permission approvals, and minimal attachments. Pairing with a remote authoritative runtime means the administrator of that runtime can see your session data. When you self-host, that administrator is you; confirm this before you connect to someone else’s runtime.