VEX / Source Control

One trunk.Every versionin motion.

VEX is source control for teams where engineers and agents build from the same trustworthy state.

Get startedRead the vision
0107
The premise

Source control is not a filing cabinet. It is a living record of decisions.

VEX makes the stable thing feel solid and every meaningful change feel visible, reversible, and ready to rejoin the whole.

Trunk-based development

Branch less.
Reconcile sooner.

A branch is a temporary question. The trunk is the answer the team agrees to keep improving.

  1. 01

    Begin at trunk

    Start from the version everyone trusts, with source, policy, and history in one shared state.

  2. 02

    Grow a leaf

    Give each human or agent change a visible workspace while it is made, tested, and challenged.

  3. 03

    Inspect in light

    Review intent, diff, checks, and operational evidence while the change is still easy to reason about.

  4. 04

    Advance together

    Reconcile early, land worthwhile work, and move the trunk forward without losing the story.

One shared system

Humans and agents. Same repository. Same account of what changed.

VEX runs on Jujutsu rather than Git's original plumbing, so parallel work can stay fluid without giving up review, policy, or an auditable path back to trunk.

Explore the agent model
01

Read

Source, history, policy, checks, runtime health, and deploy context from one graph.

02

Change

Create isolated work without turning the shared repository into a thicket of stale branches.

03

Verify

Keep tests, review, and evidence attached to the exact version they describe.

04

Land

Reconcile early and advance the shared trunk through explicit, auditable decisions.

Under the surface

A faster engine.
A clearer record.

Source, policy, workspaces, checks, releases, and runtime signals become parts of one system rather than context scattered across tools.

Engine

Jujutsu (JJ)

A modern, Git-compatible foundation built for fast rebasing and conflict recovery.

Actors

Engineers + agents

The same repository, permissions, review history, and accountable path to production.

Loop

Source + runtime

Code, checks, releases, and operational signals stay close enough to inform the next change.

Start at the trunk

Install VEX.
Clone the source of truth.

macOS and Linux builds ship on the same release train. On Windows, use the Linux CLI in WSL and keep the checkout inside the WSL filesystem.

Read the WSL guide
Install
$ curl -fsSL https://cli.cdn.vex.sc/install.sh | sh

Verify with vex --version

Build from one shared state. Keep every change legible.

Get startedTalk to the team