Remove a package

What happens

03The agent runs vibe uninstall org.vibevm.world/wal. vibe shows what will leave: the requirement line in the manifest, the lock entry, the package's folder in the dependency tree, and any dependency that only this package needed. On confirmation it removes them and regenerates the boot files, so the next agent session no longer reads the package's snippet. Your own files, including the two boot files you own and anything in vibevm/vibespecs/, are never touched.

04 Authored spec/ — written only by the node's author. Unchanged definition.

By hand

051. Remove by coordinate; the version is not needed:

vibe uninstall org.vibevm.world/wal --path hello-vibe --assume-yes

Uninstall org.vibevm.world/wal@1.0.0 — remove `vibevm/vibedeps/org.vibevm.world.wal/1.0.0` and regenerate boot.
  - removed  vibevm/vibedeps/org.vibevm.world.wal/1.0.0

Uninstalled org.vibevm.world/wal@1.0.0 — removed its vibedeps/ slot, regenerated boot.

072. Check the reading list:

vibe tree --plain --path hello-vibe

project: <TMP>/work/hello-vibe
STATIC.md: (none)
packages: 0   roots: 0
columns: load  T=transitive  C=condition  S=in STATIC.md

Removing derived state without removing packages

09Sometimes you want a clean slate rather than a smaller graph: before a build, after a tool upgrade, or to prove the tree can be rebuilt. vibe clean deletes the dependency tree and the generated boot files and keeps the manifest, the lock file, everything you wrote and the machine store. vibe clean install chains the two steps.

10 vibe clean removes exactly the derived prompt state of the workspace it runs in: (a) the dependency world — the whole vibevm/vibedeps/ root of the workspace; (b) the generated boot artifacts — vibevm/vibespecs/boot/STATIC.*, INDEX.md and INLINE.*, each carrying the generated-by-vibe marker. That is the mvn-clean analogue: what an install writes, clean deletes.

11The command refuses to run outside a project, so it cannot sweep an unrelated folder by mistake.

12 Clean refuses to run outside a vibe project (no vibe.toml at or above the cwd) — a guard against sweeping an unrelated directory.

Edge cases and rules

13Uninstalling a package that another installed package requires leaves the shared dependency in place; only packages nothing else needs are removed.

14The machine store keeps the package's bytes after an uninstall. Reinstalling it later costs no network; vibe cache clean --package reclaims the space if you want it gone from the machine.

15 The cache is accretive: a package version, once cached, is never evicted automatically.

16Removing a package does not undo what its install script did, if it had one: hook effects are not tracked, by design.

17 Only a hook's edits to materialiser-owned recorded payload are ephemeral: reinstall, update or integrity repair restores those bytes per PROP-022, then reruns hooks exactly when that payload diff is nonempty. Hook-created unrecorded state is outside .vibe-slot.toml ownership and survives by design; a rerun may compound it, so hooks must be idempotent until a separate hook-output ownership contract exists.