Glyphs that show the cache
Each task’s line shows at a glance whether it ran, was fresh, or came from a cache.
“Success” hides the most useful fact: did it run, or come back from the cache, and which one. vx’s glyph says it in one character.
Ran, up to date, restored from the local or the remote cache, failed, skipped or persistent: a broad run reads at a glance.
// what it prints
⏺ ran (cache miss)
► up to date, nothing to restore
⇢ restored from the local cache
⇣ restored from the remote cache
◼ failed
⊘ skipped, with the failure that blocked it
▸ persistent, like a dev serverMore in Output that fits
Choose how much you see
Full logs, errors only, just the hashes, or nothing.
A table of every task
One line per task at the end: what happened and how long it took.
Failures kept for later
A failure’s output is saved, so you or an agent can read it after the terminal is gone.
A run report for your PR
A short markdown report of the run, ready for a pull request or a job summary.
Every run as JSON
A JSON file per run, with each task’s result and the time the cache saved.
Label your runs
Tag a run, like env=nightly, and find it again in history and dashboards.
See where vx spends its time
A table of vx’s own stages, so a slow run points at its cause.
Output that follows the run
One task streams live; a broad run shows one line per task; CI shows everything.
Folded logs on GitHub Actions
On Actions, each task is a collapsible group with its result in the title.
Colors, on your terms
Truecolor output, turned off with NO_COLOR or forced on with FORCE_COLOR.
Exit codes in plain words
A task killed by a signal says which signal, not just a number.
Plain output in a pipe
Off a terminal, vx prints plain lines and never waits on a prompt.