Docs your agent can read
The whole site as markdown in llms.txt and llms-full.txt.
A coding agent reads markdown far better than a rendered page with navigation around it. The docs are published as plain markdown, one index and one full file.
Point your agent at them and it answers from the current docs, not from what it remembers.
// try it
curl -s https://vznjs.github.io/vx/llms.txt
curl -s https://vznjs.github.io/vx/llms-full.txtMore in See inside a run
vx why
Ask why a task re-ran, and get the input that changed.
Plan before you run
Hit or miss for every task, before anything executes.
vx show
The task exactly as a run sees it, after every preset and plugin.
vx last
Replay the last run’s summary, failures first, without running anything.
Your build as a trace
--profile writes a Chrome trace of the run.
Draw the task graph
Export the graph as Graphviz DOT and see what depends on what.
Know your workspace
One 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, queryable
Each task’s time, CPU, memory and cache result go into SQLite you can query.
Errors an agent can branch on
Under --format json, a refusal is a JSON line with a stable code.
A schema for every JSON shape
Every JSON document vx prints has a published JSON Schema.
The reference, offline
vx docs <query> searches the CLI, config and cache reference with no network.
Why a task is affected
Each task --affected keeps says which changed file or dependency brought it in.
A skill for your coding agent
An installable skill teaches an agent to run, debug and query vx.