Work offline

On a plane or behind a firewall, vibe keeps working from what the machine already holds. This page fetches what you will need before you leave and installs from it without a network.

Before I go offline, fetch into the machine store everything the VibeVM project in the current folder needs plus the package org.vibevm.world/multi-user-planning, then verify the store and show me that an offline install of this project succeeds. the vibevm skill installed for your agent; network access now; a project with `vibe.toml` `vibe cache list` shows the project's packages and the extra one; `vibe cache check` reports every entry intact; `vibe install --offline` completes without a network request vibe cache check vibe reinstall --force --offline --assume-yes

The agent runs `vibe cache add` for the extra package, which resolves it and its whole dependency closure and fetches every node into the [store](../glossary/index.xml#store) without touching the project. It runs `vibe install` once online so the project's own packages are in the store too, then `vibe cache check` to verify every stored entry against its [fingerprint](../glossary/index.xml#fingerprint). Finally it runs `vibe install --offline`: resolution and fetch are satisfied from the store alone, and the command fails loudly if anything is missing rather than installing a partial graph.

1. Warm the store with a package and its dependencies. Inside a project its [registries](../glossary/index.xml#registry) are the source; outside one, the machine-wide registries:

vibe cache add org.vibevm.world/wal Pre-warming the machine store (<TMP>/home/cache) ✓ created org.vibevm.world/wal@1.0.0 1 fetched, 0 already present — nothing materialised into any project.

2. See and verify what the store holds:

vibe cache list GROUP NAME VERSION org.vibevm.world wal 1.0.0 1 package in <TMP>/home/cache. vibe cache check Integrity sweep of the machine store (<TMP>/home/cache) 1 ok, 0 mismatched, 0 unrecorded.

3. Install without a network:

vibe install org.vibevm.world/wal --path hello-vibe --offline --assume-yes Resolving 1 root package… Materialising 1 package into vibedeps/: org.vibevm.world/wal@1.0.0 closure diff: → + org.vibevm.world/wal@1.0.0 (root-edge) → lane vibevm/vibespecs/boot/INDEX.md: 737 -> 854 B Materialised 1 package into vibedeps/; regenerated boot artifacts for 1 node(s).

The flag `--offline` on any command; the environment variable `VIBE_OFFLINE=1`; or the setting `offline = true` under `[net]` in `~/.vibe/config.toml`. The flag wins over the variable, and the variable over the setting. Online remains the default.

For a machine that never sees the registry, `vibe registry vendor` writes a folder holding every package the [lock file](../glossary/index.xml#lock-file) references, ready to be used as a [mirror](../glossary/index.xml#mirror) with a `file://` address on the other side. The fingerprints travel with it, so the mirror is verified like any other.

If an offline install refuses a package the store already holds, the project's registries were never cloned on this machine and vibe cannot learn which versions exist; one online install in any project clones them, and a `file://` mirror needs no clone at all.

Offline resolution sees the store as of its last refresh: a version published after you went offline is invisible until you are back and run `vibe registry sync` or an online install.

A package in the store is usable even when its registry no longer lists it; a package that never reached the store is a hard error naming the missing [coordinate](../glossary/index.xml#coordinate).

The program's own version manager obeys the same posture: under it `vibe self update`, `install` and `reinstall` refuse before their first request, naming the address they would have needed, and `self ls`, `current` and `which` answer from the machine as usual.