Skip to main content

Remove AITrax tracking

Use this guide to remove AITrax tracking settings. You'll preview what would be removed, then run the removal.

  • Deployment: SaaS, On-premises

Uninstall removes only AITrax-owned setup surfaces. It does not remove your repository content or unrelated configuration. The --dry-run preview works before you run it for real.

Pinning a version is not the same as removing tracking

If the goal is to stop a workstation receiving new tracker versions rather than to stop capturing, do not uninstall. On-premises, an administrator can turn on Pause automatic updates on the Automatic updates card at Settings > General > Tracker Updates, and the server withholds new tracker versions from every connected client until it is turned off. It is off by default.

1. Preview the removal​

Run the removal with --dry-run, which reports planned removals without changing files or signaling monitors:

Terminal
$ aitrax uninstall system --dry-run
▸ User-level configuration   29 would remove
✓ Done · 29 would remove, 6 unchanged · 1ms

The changed and unchanged counts reflect what setup had configured on that machine, so your own output will show different numbers. An unchanged count covers surfaces uninstall inspected and will leave alone: settings AITrax does not own, or files that are already absent. Review the reported paths before continuing. Add --verbose for a per-file report.

2. Remove the user-level settings​

aitrax uninstall system

To keep cached binaries so a later reinstall does not download them again, add --keep-cache.

3. Confirm removal​

aitrax setup check

system reports as not configured.

To confirm the background monitor process is gone as well as the configuration, check the process list. On macOS and Linux, pgrep -f "aitrax --monitor" prints nothing when no monitor is running; on Windows, Get-Process aitrax* reports no matching process.

In the portal, removal shows up as absence rather than as an event. On a work area's Tracking tab, a tool the developer no longer uses anywhere loses its green check after 7 days and shows an amber clock, then becomes an empty cell once 4 weeks have passed; the developer leaves the roster entirely once nothing they used has reported for 4 weeks. That roster tracks the person, not the machine, so removing tracking from one workstation changes nothing for a tool they still use on another. Work already captured is unaffected — it stays in the dashboards. Nothing in the portal distinguishes a removed tracker from one that is simply idle, so tell the administrator if a removal was deliberate.

If this doesn't fix it​

Contact support with all of the following:

  • The verbatim command you ran and its complete output.
  • The output of aitrax uninstall system --dry-run.
  • The output of aitrax doctor, the local diagnostic report described in the AITrax CLI reference.