DXErrors that say the fix
Errors that say the fix
A refusal under --format json now links the fix for its code, and vx docs <code> prints the same fix offline.
The reference, offline
vx docs <query> searches the CLI, config and cache reference that ships inside vx. No network, no site: the sections that match print whole, with their URL.
DXAn agent in a sandbox often cannot reach the docs site. Now the
reference travels with vx: vx docs <query> searches it on disk.
$ vx docs frozen lock --limit 1── cli.md § vx lock · https://vznjs.github.io/vx/cli/#vx-lock…It reads seven pages that ship in the npm package and the compiled
binary: cli, schema, caching, execution, patterns, security
and features. A section matches when it holds every word of the
query, and a word in its heading ranks it first. The best three print
whole; --limit changes how many.
| You ask | You get |
|---|---|
vx docs cache inputs | how a task’s inputs are declared |
vx docs exit codes | each verb’s exit codes |
vx docs sandbox allow | what a sandboxed task may touch |
vx docs ... --format json | {query, hits: [{page, heading, url, text}]} |
The JSON shape is schemas/docs.json. The guides stay on the site;
llms.txt indexes them. See the
CLI reference.
Keep reading
DXDXA refusal an agent can read
A refusal an agent can read
Under --format json, a refusal is now a JSON line with a stable code. An agent branches on VX_E_UNKNOWN_TASK, not on the wording of a sentence.
MigrationFrom npm scripts or Vite Task
From npm scripts or Vite Task
vx init turns package.json scripts into tasks, with npm pre and post hooks folded in the order npm runs them. A vite-plus repo converts the same way from its run.tasks.