Stack related work with Native Changes.
Break a larger idea into durable, dependent Changes. Each step stays independently reviewable while Vex preserves the order of the whole stack.
Explore primitiveSource control rethought for agent-led engineering teams.
Today's code hosts turn every faster agent into more pull requests, more rebases, and more work waiting on moving main. Vex rebuilds source control around parallel Changes, durable agent context, and an exact path to trunk.
One source graph
AAgent change · activeBHuman change · reviewCAgent change · stacked↓Exact candidate · queue
There's more code being produced than ever. Managing it has only got slower.
Branches and pull requests were designed for a world where changes arrived at human speed. In an agent-first team, that workflow turns abundance into contention.
- Pain point 01
Every new agent becomes another pull request.
The faster code gets written, the faster review queues fill. Work that could move in parallel becomes a growing inbox of branches waiting on one another.
- Pain point 02
Main moves. Everyone pays the rebase tax.
A change is ready, then the target moves again. Developers and agents repeatedly rebuild the same context just to keep their work landable.
- Pain point 03
The diff survives. The reasoning disappears.
A pull request shows what changed, but not the agent session, evidence, constraints, or decisions that produced it. Review starts with archaeology.
Build source control from first principles for an agent-first engineering culture.
Vex throws out the assumptions that make concurrent work fight for one branch. The source graph lets humans and agents iterate independently, preserves why each change exists, and gives reviewers exactly the insight needed to decide what lands.
Give every contributor room to move. Keep the work coherent.
These are not add-ons around Git branches. They are shared primitives for local iteration, review, provenance, and landing.
Rebase the whole stack at once.
Refresh the target and rebase the current mutable stack as one graph operation. Descendants follow their rewritten parents instead of becoming manual repair work.
Explore primitiveLand the exact candidate with the Merge Queue.
Vex orders accepted work, builds the exact candidate, evaluates its required checks, and invalidates stale speculation when the queue changes.
Explore primitiveKeep Agent Transcripts with every Change.
When an active agent session seals a Change, Vex binds its screened transcript to the exact commit so reviewers can inspect provenance and continue from a bounded handoff.
Explore primitiveAdopt Vex alongside GitHub.
Import a project without rewriting its source, project Vex Changes to stable GitHub pull requests, and keep GitHub in the loop while the team evaluates Vex.
Explore primitiveRun Vex natively when you are ready.
Use Vex and its Jujutsu-native graph directly: durable Change identity, local stacking, hosted review, policy, and landing share one source model.
Explore primitiveLet the agent iterate. Give the human a decision, not a mystery.
Vex carries the change, its dependency graph, its evidence, and its agent context through the workflow so speed does not come at the cost of understanding.
- 01
Agent iterates
The agent reads, edits, tests, and revises inside a mutable Change.
- 02
Vex preserves the work
Code, dependency, patchset history, checks, and the screened agent session stay connected.
- 03
A human gets the right view
Review the focused diff, its place in the stack, and the context behind the decisions.
- 04
The exact candidate lands
The queue validates the code against the trunk state it will actually join.
Rebase the mutable stack
$ vex pull --rebase --dest mainSubmit the Change for review
$ vex submit --target mainThe stack stays legible while the work keeps moving.
In Vex, each Change keeps a durable identity while the graph records its parents, position, checks, review state, and landing closure.
Real Change detail
One durable Change connects checks, review state, and every dependent member that must land with it.
This evidence shows a single-repository stack in the Vex organization.
/vex/change/625
Vex organization · 11 Aug 2026
Meet your team where it is. Build toward where it needs to go.
Work with GitHub
Import without rewriting the source and project Vex Changes into stable pull requests. Start with one representative project, preserve the GitHub path, and expand only when the workflow proves itself.
Run Vex natively
Give humans and agents the native Change graph directly—without making branches and pull-request conventions the source of truth.
Help build the place where software gets built next.
We are building Vex with the teams already feeling the limits of branch-first source control. Bring us the messy stacks, the rebasing nightmares, and the agents moving faster than your review process.