vx show prints a task the way the run sees it. Presets, plugins and
computed commands are already applied.
$ vx show packages/a#build
─ packages/a#build ───────────────────────────────────────────
dir packages/a
command bun build src/index.ts --outdir dist
inputs.files src/**
outputs.files dist/**
This is what the cache key is built from. If a preset set outputs or
a plugin changed the command, you see it here.
It reads the same file the run reads
vx show reads the lock file, like vx run. Change a config, run
vx lock, and the change shows.
Every project on one screen
$ vx show
project dir tasks
packages/a packages/a 7 tasks
packages/b packages/b 4 tasks
packages/c packages/c 5 tasks
packages/d packages/d 2 tasks
vx show --affected lists the projects your change reaches, without
running anything.
Demo workspace · vx 69617eb · 2026-10-23
JSON for scripts and agents
{"name":"packages/a","dir":"packages/a","task":"build","config":{"exec":{"command":"bun build src/index.ts --outdir dist"},"inputs":{"files":["src/**"]},"outputs": {"files":["dist/**"]}, "cache": true}}
--format json prints the object. On this repository that is 13
projects and 201 tasks in 5,807 bytes.
Reference: the CLI. More at
vznjs.github.io/vx.
Originally published on the vx blog. vx is open-source (MIT) task orchestration with a build cache: vznjs.github.io/vx · GitHub.
Written with AI assistance.
Top comments (0)
Some comments may only be visible to logged-in visitors. Sign in to view all comments. Some comments have been hidden by the post's author - find out more