Skip to main content
Vibex records changes per release. Each version page summarizes the highlights, new features, fixes, and internal work in that release range. The short hashes at the end of an entry point to commits in vibex-ai/vibex so you can trace the evidence.
Vibex is still in the 0.1.0 candidate phase. The newest release is 0.1.0-rc.8. Packages and download links follow GitHub Releases.

​
Releases

v0.1.0-rc.8

October 18, 2026 · 723 commits · The Vibex TUI terminal client, Agent teams, scheduled sends, custom workbench backgrounds, Agent computer use, a rebuilt mobile client, and automatic updates on by default.

v0.1.0-rc.7

September 29, 2026 · 92 commits · A browser in the workbench that Agents can drive, page-to-code jumps both ways, Prompts as a first-class object, the Skill market on ClawHub, fewer idle repaints, and the GPUI kit at 0.7.0.

v0.1.0-rc.6

September 23, 2026 · 96 commits · Session groups and split workspaces, MCP and Skill marketplaces, notifications you can act on, named runtimes and devices, managed Agent rollback, and camera-first mobile pairing.

v0.1.0-rc.5

September 20, 2026 · 95 commits · Goals as part of the session, a preview panel that can detach into its own window, the workbench command palette, automatic updates with release notes, native steering, and twenty built-in palettes.

v0.1.0-rc.4

September 17, 2026 · 45 commits · Ten light and dark themes, a floating window frame, one runtime manager, a rebuilt model picker, and terminal and search performance fixes.

v0.1.0-rc.3

September 12, 2026 · 91 commits · The remote authority takes over the workbench, connection-link pairing, the gpui-kit migration, and model limits.

v0.1.0-rc.2

September 10, 2026 · 42 commits · The cloud headless runtime, desktop client mode, cloud deployment, and the mobile overhaul.
v0.1.0-rc.1 was the first release candidate and has no separate release note; see the commit history at that tag.

​
How to read a release page

  • Highlights — the most important behavior changes in the release.
  • New Features — what the release adds, grouped by the product surface it affects.
  • Fixes — corrected issues, grouped by the surface they affect.
  • Performance — improvements to responsiveness and resource use.
  • Internal, Build & Docs — dependency bumps, build and release plumbing, documentation, and specs.
The short hash at the end of an entry, such as (ec6e378), identifies the commit on GitHub.