VEX / The workflow

Ship agent-generated code without losing control.

VEX turns parallel work from developers and coding agents into small, evidence-backed changes — so safe work keeps moving and people focus on the decisions that matter.

Start with VEXSee the workflow

01 / The problem

Code is becoming abundant. Trusted change is becoming scarce.

Developers can now direct many agents to explore, implement, and test in parallel. The bottleneck moves downstream: overlapping work, unclear dependency order, reviewer overload, and a weak connection between a release and the evidence that supported it.

VEX keeps the team in motion without asking anyone to become the human routing layer. It preserves the structure around each proposed change, chooses the right approval path, and makes the final decision legible.

The VEX workflow

Keep creation fast. Make promotion deliberate.

VEX begins after code is created: when a team needs to decide what can move, who should decide, and what must be true before it reaches production.

A workflow from code created by developers and agents into VEX, where small stacks are assessed for risk, routed either to evidence-backed auto-approval or guided human review, then landed and shipped. A control layer of policies, risk routing, approval gates, evidence, decisions, and traceability applies throughout.
  1. Developers and agents create code, tests, and task context in parallel.
  2. VEX preserves related work as small, dependent stacks with intent and landing order.
  3. VEX assesses tests, affected files, owners, and policy within and across stacks.
  4. Low-risk work can move when the required evidence and policy are present.
  5. Higher-risk work goes to guided human review with intent, context, critical code, and risks.
  6. Approved stacks land independently in dependency order, then connect to the release.

02 / Build, review, ship

Build without blocking. Review without reconstructing. Ship without coordinating by hand.

VEX gives agents room to work, gives people the context to decide, and gives approved changes a deliberate path forward. The change gains context as it moves; it never loses its relationship to the trunk.

The VEX Build, Review, Ship loop. Build preserves stackable changes, workspaces, agent tooling, and Git compatibility. Review keeps change history, stack context, checks, approvals, and optional GitHub projection with the decision. Ship lands submitted work in dependency order with target freshness, checks, approvals, and a landing record.

The signals trace a quiet, continuous path from proposed work to a recorded landing. The full explanation remains present when motion is disabled.

  1. Build: VEX Source Control and Changes give agents stackable, identifiable work in beta today.
  2. Review: the decision keeps its intent, dependencies, checks, approvals, and GitHub projection where configured.
  3. Ship: landing keeps the submitted scope, dependency order, target freshness, and evidence together; release grouping and deployment signals are next.

03 / What changes

  1. 01

    Move faster

    Safe work should not wait behind unrelated work.

    Small, explicit stacks reduce the rebase churn and manual coordination that make parallel authoring feel slower than it should.

  2. 02

    Focus human judgment

    People should review the decision, not reconstruct the story.

    When a change needs a person, the intent, relevant code, evidence, dependencies, and risks arrive together instead of being scattered across agent output and CI.

  3. 03

    Stay accountable

    Every release should have a defensible record.

    Intent, policy, evidence, approval, landing, and outcome stay connected so a team can explain what moved and why.

Built in stages

Be precise about what is live and what is next.

Live in beta

VEX Source Control, Changes, review, and landing are available today.

Arriving in stages

Risk-based automation, deployment, and end-to-end release traceability are the workflow VEX is building toward.

Keep exploring

More agents should not mean more coordination.

VEX turns parallel agent output into software a team can confidently ship.

Explore ChainingRead The Source Control Docs