Help
Uninstall software only
Preview the exact Atlas-owned paths, then apply. Your boards and backups are not part of that plan.
tracker uninstall removes Atlas-owned software. Boards, history, backups, and registry pointers stay so a later install can rediscover them.
Preview, then apply
tracker uninstall tracker uninstall --yes
--apply is an alias for --yes. Default is a digest-bound preview. Without a verifiable install receipt, uninstall refuses to delete files. Package-manager installs print the manager command instead of unlinking a Cellar path. /uninstall in the tracker shell is the same command.
For a source build or go install, a successful tracker init or tracker setup records the running Atlas binary and its hash when ownership can be verified. An existing receipt for another installation is preserved. If the binary changes after the receipt was written, uninstall refuses removal until a verified setup refreshes the source receipt. There is no force-delete option.
What stays
- Workspaces,
projects/,.tracker/, tickets, events - Backup repositories, history, targets
- Registry pointers
- Unrelated client config and other agents
Removing the binary by hand still leaves repository data in place. Prefer tracker uninstall so managed Home units and Atlas-owned MCP blocks are in the plan.