Skip to main content
Vibex ships ready-made artifacts for the desktop, Android, iOS, and self-hosted services. End users do not need Rust, Node.js, or pnpm: the desktop installers are self-contained, and the TUI ships with them. Every artifact lives on the same page:

Download the latest release

Open the GitHub Releases latest page and pick the artifact for your platform.
Vibex is still in a candidate phase: besides stable builds, releases may be -rc.N or -preview.N prereleases. The latest page resolves to the newest one; use the full release list for a specific version.

​
Desktop

The Linux .deb depends on libvulkan1, libxcb1, libxcb-xkb1, libxkbcommon0, libxkbcommon-x11-0, libdbus-1-3, libfontconfig1, and an appindicator library (libayatana-appindicator3-1 or libappindicator3-1). The distribution’s package manager usually resolves these.
macOS and Windows packages are currently unsigned.
  • macOS blocks the first launch with Gatekeeper: Control-click the app in Finder, choose Open, and confirm; or run xattr -d com.apple.quarantine /Applications/Vibex*.app.
  • Windows shows a SmartScreen prompt: choose More info → Run anyway.
These prompts come from the missing signing certificate, not from a bad package. Each artifact has a .sha256 sidecar, and SHA256SUMS lists every digest.

​
Release channels

Desktop packages carry a compile-time channel identity. Channels can be installed side by side: Each channel has its own SQLite database and configuration. Switching channels does not migrate data; configure Agents and Providers again after installing a different channel. The channel is part of the package and cannot be changed in the app.

​
Upgrade

The desktop has signed automatic updates, on by default. In Settings → General or Settings → About → Software update:
  • The app checks about 30 seconds after launch, then every 2 hours on RC / Preview and every 6 hours on Stable.
  • The manifest is verified with Ed25519 and each artifact with SHA-256; a failed check never installs.
  • With automatic updates on, a discovered release downloads automatically; install it in-app or when you quit.
  • With Automatic updates off, a discovered release waits for your confirmation. With Update prompts off, the title-bar button and panel are hidden, but background checks still run.
  • Installation depends on the package: AppImage replaces itself in place; .deb, macOS .app, and NSIS launch the system installer and need a restart.
Only same-channel versions are accepted: an RC build sees only -rc.*. If automatic updates are unavailable, install a newer package over the old one.

​
Android

Sideload the Android client from GitHub Releases:
  1. Download vibex-<version>-android-arm64.apk.
  2. Allow installs from that source in system settings.
  3. Open the APK to install (application id ai.vibex.mobile).
Android has no app store, so updates use the same release manifest:
  • The client follows the Stable channel only; a prerelease install still learns about the stable release it leads to.
  • The app verifies the manifest signature and the APK’s SHA-256, then hands the staged file to the system installer; Android enforces signing-key continuity.
  • You can download and install in the app, or open the signed download in a browser.
  • If the new APK has a different signing key, Android refuses the update. RC / Preview releases use an ephemeral CI key when no repository key is configured, so different RCs may require uninstalling first; uninstalling clears local pairing credentials.
Stable releases require a fixed Android release key. Without it the release pipeline fails rather than publishing a build that cannot update in place.

​
iOS

iOS artifacts include:
  • vibex-<version>-ios-unsigned.ipa: a complete arm64 device build, unsigned.
  • vibex-<version>-ios-simulator.app.zip: an unsigned simulator build.
  • vibex-<version>-ios-xcframework.zip: for integration.
iOS refuses to run unsigned code, so the device IPA must be re-signed with the installer’s own Apple ID. A free Apple ID signature lasts seven days; re-sign when it expires. Common install paths: See the Unsigned iOS install guide for the full re-signing and verification steps.
Re-signing replaces the signature entirely; it proves nothing about who built the binary. Only install an IPA from a source you trust.

​
TUI

The Vibex TUI ships inside every desktop package: Run vibex in a project directory. See Vibex TUI.

​
Self-hosting

When you need cross-network access, or do not want session data on an always-on personal computer, self-host the runtime:
  • Self-hosted headless runtime — vibex-server has the same capabilities as the desktop runtime and is suited to a server or always-on machine.
  • SSH and WSL remote runtimes — let the desktop install the runtime on another machine over SSH, or run it inside WSL2.
  • Self-hosted Relay — forwards end-to-end encrypted frames only; it is not an authorization or business-data boundary.
Both the server and the Relay publish multi-architecture container images (linux/amd64, linux/arm64).

​
Build from source

See Build from source when you need to change code or your platform has no artifact.

​
Uninstall

Uninstalling does not delete the data directory. To remove everything, read Privacy and recovery, then delete the channel’s data directory.