Frequently asked questions
Where are the files my command wrote?
Staged beside your working tree, not written into it. A build that succeeds under Vanish leaves your build directory as it was until you apply the result. vanish results lists staged results, and vanish results apply TOKEN writes one into your tree. To write results in as each Run finishes, add --apply to the command, or put apply = true in .vanish.toml at the root of your repository. Run your first command walks through it.
Why did my first run take so long?
The first run in a repository uploads and hashes the whole tree: about a minute and a half on a 27 GB tree. Later runs send only what changed, and Vanish adds roughly a second to a command in a normal repository.
Why does my Node project fail with Cannot find module?
Your laptop's node_modules is not sent with a Run, and dependencies installed in one Run do not carry over to the next, so running vanish npm ci and then vanish npm test still fails. Install and test in the same Run:
vanish sh -c "npm ci && npm test"Python virtual environments stay behind the same way, and pip is not preinstalled; toolchains lists what the worker has.
Will my command finish sooner?
One command, no. Each Run adds startup and transfer time, so a single command is slower than on a fast laptop: a cold release build of ripgrep took 1.5 times as long under Vanish as on a 16-core M4 Max, and a bare echo took about a second instead of a few milliseconds. Several at once, yes: each Run gets its own worker instead of sharing your laptop's cores, so from three simultaneous builds Vanish finished first, and four finished in 14 seconds instead of 24. Either way the work leaves your laptop: that cold build used 358 times less of your laptop's CPU.
How does the price compare with running my own VM?
A VM you run yourself is cheaper: the default Vanish machine costs about 1.56 times the on-demand price of the same shape on AWS. Pricing sets out what the difference buys, and who should run their own VM instead.
What happens to my files if I stop using Vanish?
You keep them. vanish materialize extracts every byte you have ever made, any day, logged in or not. The snapshot engine runs on your machine without an account or a network connection, so you can check this yourself from any directory:
TOKEN=$(vanish snapshot --source . --store ~/vanish-store | grep -o 'vanish3:[^"]*')
vanish materialize --snapshot "$TOKEN" --store ~/vanish-store --destination ~/vanish-restoredCan I run a macOS-only program?
No. Workers run Linux. Use a Linux build of the program, and install what it needs with a toolchain.
Do I need to commit my changes?
No. Each Run uses your working tree as it is, uncommitted changes included. Working trees and results lists what is left out.
Does a failed command lose its output files?
No. Whatever a failed command wrote is staged like any other result, so you can inspect and apply partial output. If Vanish itself fails, the Run produces no result and is reported as a Vanish error, with an ID to bring to the Discord.
Can I use it from CI?
Yes. Provide VANISH_TOKEN from your CI secret store; see login. Runs from CI draw on the same credits and concurrent Run limit as your other Runs.