See inside a run
Every key, plan and past run, on request.
Ask vx why a task ran, what a run would do, or where the time went, and get an answer you can read or a JSON value an agent can use.
15 features
vx whyAsk why a task re-ran, and get the input that changed.“Why did this re-run?” is the most expensive question in a monorepo. vx records every part of every cache key on a miss, so it can answer it.
Plan before you runHit or miss for every task, before anything executes.A task’s key folds in its dependencies’ input keys, never their outputs. So every key in the graph is known before the first task starts.Each one has a page that shows it working.
vx showThe task exactly as a run sees it, after every preset and plugin.
vx lastReplay the last run’s summary, failures first, without running anything.
Your build as a trace--profile writes a Chrome trace of the run.And 10 smaller things that add up.
Draw the task graphExport the graph as Graphviz DOT and see what depends on what.Know your workspaceOne command shows versions, projects, cache size and recent runs.JSON from every report
show, info, why, last and cache all print JSON, so scripts and agents never parse text.Every run, queryableEach task’s time, CPU, memory and cache result go into SQLite you can query.Errors an agent can branch onUnder --format json, a refusal is a JSON line with a stable code.A schema for every JSON shapeEvery JSON document vx prints has a published JSON Schema.Docs your agent can readThe whole site as markdown in llms.txt and llms-full.txt.The reference, offlinevx docs <query> searches the CLI, config and cache reference with no network.Why a task is affectedEach task --affected keeps says which changed file or dependency brought it in.A skill for your coding agentAn installable skill teaches an agent to run, debug and query vx.