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.
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.
DXAn agent that runs vx run build --format json reads stdout. When vx
refused the run, stdout used to be empty, and the reason sat on stderr
as prose. Now the refusal is on stdout too, as one JSON line:
$ vx run biuld --all --format json{"ok":false,"error":{"code":"VX_E_UNKNOWN_TASK","message":"vx run: no projects declare task(s): biuld. Did you mean build?"}}The exit code is still 1 and stderr still says it in words. The code is the contract; the message may change.
| Code | Means |
|---|---|
VX_E_USAGE | A flag or argument vx does not take |
VX_E_UNKNOWN_TASK | No project declares the task |
VX_E_CONFIG | A config that does not load |
VX_E_CYCLE | The task graph has a cycle |
VX_E_NO_WORKSPACE | No workspace above the working directory |
VX_E_REFUSED | Any other refusal |
VX_E_INTERNAL | A bug in vx |
schemas/error.json describes the line, and the full table is in the
CLI reference.
Keep reading
DXDXThe reference, 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.
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.