Setup

Remove Vigilance on Linux

Use these steps when the Vigilance program does not run, or when you want to remove it with tools that are already on your Linux computer or Chromebook. They need no Vigilance program and no admin password.

If the program runs

Not sure about these steps? Send this page to your IT provider, or write to support@vigihq.com.

Open a terminal window. On a Chromebook, open the Terminal app and choose penguin. Then paste this line and press Enter: ~/.vigi-seat/Vigilance uninstall. It does every step below. Your company can also remove this computer in its Portal. Vigilance then turns off within about 6 minutes and removes itself within 30 days.

For other systems, see Remove Vigilance on a Mac or Remove Vigilance on Windows.

1. Stop the background items

Vigilance runs two background items: the program, which starts at login, and a small watchdog job. They are systemd user files. This stops each one:

systemctl --user disable --now vigilance-restore.timer vigilance-restore.service vigilance.service

Your system chooses the folder of the unit files. This command prints the files. The first line of each one names its file:

systemctl --user cat vigilance.service vigilance-restore.service vigilance-restore.timer

Delete those three files and the file vigilance.env in the same folder. Then tell systemd that the files are gone:

systemctl --user daemon-reload
systemctl --user reset-failed

2. Put back your package settings

Vigilance pointed npm, pnpm, yarn, bun, pip and uv at 127.0.0.1:24873. It changed only its own lines in your user files. This lists every line that still names that address:

grep -rn "127.0.0.1:248" ~/.npmrc ~/.yarnrc ~/.yarnrc.yml ~/.bunfig.toml ~/.config/pip ~/.config/uv ~/.config/pnpm "${XDG_CONFIG_HOME:-$HOME/.config}" 2>/dev/null

Each line keeps your old value in a comment next to it. Put the old value back. If there was no old value, delete the line. The restore copy has every old value too, in ~/.local/state/vigilance/restore.json. Delete the line noproxy=127.0.0.1,localhost from ~/.npmrc if Vigilance added it.

3. Delete the saved credential

Each computer has a device credential. On Linux it is a file in the folder of step 5, so there is nothing separate to delete.

4. Take out the hooks and the notes

Vigilance adds a short note to the instruction file of Claude Code, if Claude Code is on the computer. The installer result screen names every file that got a note. If it names none, skip this step.

Open each file. Delete the block that starts with <!-- vigilance:start --> and ends with <!-- vigilance:end -->. Delete the Vigilance entry in the hooks or settings file of that tool.

5. Delete the files

rm -rf ~/.vigi-seat ~/.local/state/vigilance

6. Check, and tell your company

systemctl --user list-unit-files 'vigilance*'
npm config get registry
pip config list

The first command lists no unit. The others print the registries you used before Vigilance. Then ask your company to remove this computer in its Portal, so your bill drops by one computer. On Solo, sign in to your Portal at app.vigihq.com and remove the computer there.

In WSL, also ask your company to remove "Linux in WSL" in its Portal.