Remove Vinculum from a computer

There are two ways out. Removing Vinculum from the app takes everything off the computer. Uninstalling the app the usual way keeps this computer's sign-in, so a reinstall picks up where it left off.

Remove everything, from the app

Open Vinculum, go to Settings, and under This computer choose Remove Vinculum from this computer. It shows you what it will remove first, and nothing changes until you press Remove.

It signs this computer out of your account and stops the runner, the program that does Vinculum's work in the background. It takes the runner out of startup and deletes what Vinculum keeps on this computer: its settings, the copies of your projects it downloaded, its logs, and the hooks it added to Claude Code. Your own folders are not touched. Then the app closes.

If work is running

Removal waits while jobs are running on this computer. Let them finish or stop them, then try again.

If the server can't be reached to sign this computer out, nothing is removed, and the app offers Remove anyway. This computer then stays listed on your account until you remove it there, as described below.

The app itself stays installed. Remove it the usual way for your system, described next.

Remove everything, from a terminal

If you installed only the runner, or the app isn't there, the runner removes itself. On its own, the command lists what it would remove and changes nothing:

bash

vinculum-runner uninstall

To remove it:

bash

vinculum-runner uninstall --yes

If the server can't be reached, it stops with nothing changed. To remove it anyway, add --offline:

bash

vinculum-runner uninstall --yes --offline

On Windows a running program can't delete itself, so the runner leaves its own file behind. Delete %LOCALAPPDATA%\Vinculum\vinculum-runner.exe once the command has finished.

Remove just the app

Windows: Settings, Apps, Installed apps, then Uninstall next to Vinculum.
Linux, .deb: sudo apt remove vinculum
Linux, .rpm: sudo dnf remove vinculum
Linux, AppImage: delete the AppImage file.
macOS: move Vinculum from Applications to the Trash.

On Windows and with a Linux package, this stops the runner and takes it out of startup, and keeps this computer's sign-in and settings, so a reinstall signs straight back in. An AppImage and the macOS Trash run nothing on the way out, so the runner keeps running and keeps its place in startup. To take everything, use Remove Vinculum from this computer before you remove the app.

If the computer is still listed on your account

A computer that couldn't reach the server when it was removed, or one you no longer have, still shows on your account. On the dashboard, open Settings, then Machines, and choose Revoke pairing on it. It can't do any more work for you after that.

Remove a self-hosted server

If you installed your own server with curl -fsSL https://vinculum.run/install/server | sh, take it off in this order. If this machine also runs the Vinculum runner, remove it first (above): it keeps its repo clones and worktrees in the same data folder, and the last step deletes that folder.

Stop vinculum run with Ctrl-C.
The built-in database keeps running after the server stops, and uninstalling doesn't stop it either. Stop it while its files are still there. On Linux:
bash
```
kill "$(head -1 ~/.local/share/vinculum/pgdata/postmaster.pid)"
```
On macOS:
bash
```
kill "$(head -1 "$HOME/Library/Application Support/vinculum/pgdata/postmaster.pid")"
```
If you set VINCULUM_EMBEDDED_PGDATA, or XDG_DATA_HOME on Linux, the database's folder is there instead; use that path.
To keep your data, copy that pgdata folder somewhere safe now that the database has stopped.
Uninstall the server, and the bridge tool the installer added beside it:
bash
```
uv tool uninstall vinculum-run
uv tool uninstall fastmcp-remote
```
Delete the config and data. On Linux:
bash
```
rm -rf ~/.config/vinculum ~/.local/share/vinculum
```
On macOS both live in ~/Library/Application Support/vinculum:
bash
```
rm -rf "$HOME/Library/Application Support/vinculum"
```

If the installer put uv on the machine for you, it's still in ~/.local/bin. Leave it if anything else uses it.