Local storage

Vsync separates its reusable cache from materialized checkouts.

Default locations

The cache defaults to <build-root>/.vsync-cache. Override it with --store or VSYNC_STORE. The desktop app and CLI use the same cache.

The build root is the parent directory for checkouts created without an explicit --out path:

vsync root
vsync root D:\builds

Changing the build root selects a new default cache. Existing cache data in the previous root is left in place.

Plan free space

The cache stores reusable chunks, while each checkout stores a complete materialized build. Both consume disk space. During an update, Vsync keeps the old checkout until its replacement is staged, so peak usage can include the cache, old checkout, and new checkout at once.

Setting the root marks the directory for the server you are logged in to (a .vsync-root.json file inside it). A root belongs to one server; use a different directory for each server you work with.

Inspect the cache

vsync cache status

Prune old cached builds

Preview first:

vsync cache prune --keep-builds 3 --dry-run

Then reclaim the space:

vsync cache prune --keep-builds 3

Pruning keeps the selected newest cached build manifests and all chunks they need. A remote build can be downloaded again later.

Clear the cache

vsync cache clear --yes

This removes cached manifests and chunks but leaves materialized checkouts on disk. Do not clear the only copy of a local build that has not been uploaded.