Remove a package

Removing a package takes its text out of the project and out of the agent's reading list, and leaves everything you wrote untouched.

Remove the package org.vibevm.world/wal from the VibeVM project in the current folder and confirm that nothing of it remains in the reading list. the vibevm skill installed for your agent; a project in which the package is installed the requirement is gone from `vibe.toml`, the entry is gone from `vibe.lock`, the package's folder is gone from `vibevm/vibedeps/`, and `vibe tree` no longer lists its snippet; `vibe check` reports no errors test ! -e vibevm/vibedeps/org.vibevm.world.wal vibe check --quiet

The agent runs `vibe uninstall org.vibevm.world/wal`. vibe shows what will leave: the requirement line in the [manifest](../glossary/index.xml#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](../glossary/index.xml#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.

1. Remove by [coordinate](../glossary/index.xml#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.

2. 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

Sometimes 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](../glossary/index.xml#lock-file), everything you wrote and the machine [store](../glossary/index.xml#store). `vibe clean install` chains the two steps.

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

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

The 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.

Removing a package does not undo what its install script did, if it had one: [hook](../glossary/index.xml#hook) effects are not tracked, by design.