Remove Vigilance on a Mac

If the program runs

Run ~/.vigi-seat/Vigilance uninstall. It does every step below. Your company can also remove this computer on its owner page. Vigilance then turns off within about 6 minutes and removes itself within 30 days.

Removing it by hand is for the day the program does not run. It is also for anyone who wants to check, line by line, that nothing of it is left. For Windows, see 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. Both file names in ~/Library/LaunchAgents contain vigi. This stops each one and deletes its file.

for f in ~/Library/LaunchAgents/*[Vv]igi*.plist; do
  launchctl bootout "gui/$(id -u)" "$f"
  rm "$f"
done

If the shell says it found no match, no Vigilance background item is left. Then open System Settings, General, Login Items, and check that no Vigilance item is listed.

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:24873" ~/.npmrc ~/.yarnrc ~/.yarnrc.yml ~/.bunfig.toml ~/.config/pip ~/.config/uv ~/.config/pnpm ~/Library/Preferences/pnpm "$HOME/Library/Application Support/pip" 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 ~/Library/Application Support/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. It sits in the Keychain, or in a file in the folder of step 5. This removes the Keychain items:

while security delete-generic-password -s vigihq.com/vigi-seat >/dev/null 2>&1; do :; done

4. Take out the hooks and the notes

Vigilance can add a short note to the instruction file of each AI tool it finds. On a paid plan, it also adds a hook to the user settings of that tool. 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. Leave every other line as it is. Vigilance adds only that block to these files.

5. Delete the files

rm -rf ~/.vigi-seat "$HOME/Library/Application Support/Vigilance"

The folder /Users/Shared/Vigilance holds one small file, computer.json, that every account on the Mac can read. Delete the folder when no other account on this Mac uses Vigilance.

6. Check, and tell your company

launchctl list | grep -i vigi
npm config get registry
pip config list

The first command prints nothing. The others print the registries you used before Vigilance. Then ask your company to remove this computer on its owner page, so your bill drops by one computer.