vx speaks to agents
vx run speaks JSON, every refusal has a stable code, and vx mcp plans and runs tasks. vx init moves a Turbo or Nx repo to vx in one command.
Read the post// vx releases
Releases
What each version of vx changed, with the stories behind the big ones on the blog.
Runs that explain themselves
A live run now says how long is left, vx why follows a re-run to the file that caused it, and a bad config points at its line.
Every cache key known before a task runs
Two workspace rules that let vx know every key before anything runs, servers that stay off when only cache hits need them, and a live OpenTelemetry export.
One cache for every checkout
The cache moves to ~/.vx and is shared by every checkout of a repo, --affected follows task edges, and npx @vzn/vx-migrate does the whole adoption.
Ready for Docker and pull requests
vx prune cuts a workspace and its lockfile for a Docker build, projects take tags you can filter on, and remote cache writes can be scoped per pull request.
The Turbo and Nx flags you already type
vx 0.0.326 to 0.0.360 migrate Nx executor targets as the commands they run, accept the --filter and flag spellings Turbo, pnpm and Nx users already type, and cut a scoped run on 1,000 projects from 181 ms to 113 ms.
Fewer surprises when you switch
vx init maps a root package.json's repo-wide scripts, a bare --affected takes its base from affectedBase, and Turbo and Nx commands, flags and cache switches now land where you expect.
Starts 2× faster
turbo() now runs root tasks, single-package repos and with sidecars as Turbo does, nx() finds every project in an integrated repo, and the CLI starts 2× faster.
Start from Turbo or Nx in one line
vx init now sets up a Turbo or Nx repo with one plugin line, the workspace root can hold tasks, and vx last jumps straight to the run that failed.
Affected runs that include dependents
nx() maps an Nx project graph to vx tasks with nothing written, --affected selects dependents too, and remote caches stream artifacts instead of holding them in memory.
The foundation
The first 21 releases built the foundation: a TypeScript task graph with a content-addressed cache, a sandbox that proves what a task reads, and plugins for remote caches, telemetry and adoption.