Skip to main content

AITrax CLI reference

aitrax is the native command that performs all AITrax setup and diagnostics. Commands are grouped by what they change. The commands the tracker runs on its own — the hook, harvest, and MCP server entry points — are not listed here.

Setup commands​

The following table lists the setup commands:

CommandPurpose
aitrax setup systemConfigure user-level native tracking settings
aitrax setup checkPrint native setup status. It repairs two settings as it runs, so it is not read-only
aitrax setup reconcileSelf-heal user-level setup drift after an update. No effect unless setup already completed and a surface is missing. Absent from aitrax setup --help

Uninstall commands​

The following table lists the uninstall commands:

CommandPurpose
aitrax uninstall systemRemove user-level tracking settings
aitrax uninstall repoRemove repository-level tracking settings, including this worktree's entry in the registry
aitrax uninstall allRemove user-level and repository-level tracking settings

The following table lists the flags these commands accept:

FlagPurpose
--dry-runReport planned removals without changing files or signaling monitors
--verbose, -vPrint a per-file report of what uninstall changed. Combine with --dry-run for the path inventory described in Files and locations
--keep-cachePreserve the cached AITrax binaries and full artifacts

See Remove AITrax tracking.

Diagnostic commands​

The following table lists the diagnostic commands:

CommandPurpose
aitrax doctorPrint lifecycle diagnostics. Emits the same JSON status document as aitrax setup check, including the path to the repository registry, but changes nothing on the machine. Support tickets ask for its output
aitrax healthOffline diagnostic rollup of the shared tracker lifecycle log. Prints a verdict, the event span, and a recent-activity table
aitrax versionPrint the embedded build version

The following table lists the flags aitrax health accepts:

FlagPurpose
--path <dir>Read the lifecycle log from a directory other than the default
--jsonEmit the rollup as JSON instead of the table
--since <duration>Set the lookback window the verdict is computed over, in place of the default
--allDrop the lookback window and include every retained event
--verbose, -vInclude per-event detail