Remove Vigilance on Windows

If the program runs

Run %USERPROFILE%\.vigi-seat\Vigilance.exe 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 a Mac, see Remove Vigilance on a Mac.

1. Stop the background items

Vigilance starts at logon from a scheduled task, and a second task checks on it. Both task names contain vigi. This stops the program, then removes both tasks and any logon entry that points at the Vigilance folder:

Get-Process | Where-Object { $_.Path -like "*\.vigi-seat\*" } | Stop-Process -Force
Get-ScheduledTask | Where-Object { $_.TaskName -match "vigi" } | Unregister-ScheduledTask -Confirm:$false
$run = "HKCU:\Software\Microsoft\Windows\CurrentVersion\Run"
(Get-ItemProperty $run).PSObject.Properties | Where-Object { $_.Value -like "*\.vigi-seat\*" } | ForEach-Object { Remove-ItemProperty -Path $run -Name $_.Name }

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:

Select-String -Path "$env:USERPROFILE\.npmrc","$env:USERPROFILE\.yarnrc","$env:USERPROFILE\.yarnrc.yml","$env:USERPROFILE\.bunfig.toml","$env:APPDATA\pip\pip.ini","$env:APPDATA\uv\uv.toml" -Pattern "127.0.0.1:24873" -ErrorAction SilentlyContinue

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 %LOCALAPPDATA%\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 in Windows Credential Manager. Its name starts with vigihq.com/vigi-seat. This lists it. Then delete each name that it prints after target=:

cmdkey /list | Select-String "vigihq.com/vigi-seat"
cmdkey /delete:<name that follows target=>

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

Remove-Item -Recurse -Force "$env:USERPROFILE\.vigi-seat","$env:LOCALAPPDATA\Vigilance"

The folder C:\ProgramData\Vigilance holds one small file, computer.json, that every account on the computer can read. Delete the folder when no other account on this computer uses Vigilance. If Settings, Apps still lists Vigilance, remove that entry there.

6. Check, and tell your company

Get-ScheduledTask | Where-Object { $_.TaskName -match "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.