How to uninstall T3 Code on Mac
Save and commit your T3 Code work before removing the desktop app. The official project documentation distinguishes desktop, CLI and background-service installations, and uses independently installed coding agents. Keep project files, worktrees and agent session archives unless you intend to remove them separately.
Quit and remove the app
Stop agent tasks and quit T3 Code. Move T3 Code (Alpha).app from Applications to the Trash. If you separately installed a t3 service, use its own documented service controls before retiring that installation; deleting the desktop app does not prove the service has stopped.
Review local data
After stopping desktop agent tasks and quitting T3 Code, open the exact paths below with Finder Shift + Command + G. Copy wanted data outside the folder before removal, then move only the items you no longer need to the Trash. Skip missing paths and leave shared parent folders alone.
~/.t3/userdatawas observed in the test and is in the cask zap list; copy wanted desktop state before removing it.~/Library/Application Support/T3 Code (Alpha)is another current cask data target.- Keep worktrees, repositories and provider session archives separately. The two named data folders do not authorize deleting the entire
~/.t3tree or every coding-agent directory.
Check the result
pgrep -ifl "T3 Code|t3code"
command -v t3
ls -ld "/Applications/T3 Code (Alpha).app" "$HOME/.t3/userdata"
No process output means this name was not found, not that every helper has gone. Check any match against the app’s actual executable path. A missing-path error from ls means only that location is absent; permission errors leave its state unknown. A surviving folder can be intentional data to keep.
Output from command -v shows a CLI still reachable through your PATH; no output does not prove that every independently installed copy is gone.
If you installed it with Homebrew
The cask has no separate uninstall helper. Zap includes ~/.t3/userdata, the desktop support folder, caches, HTTP storage, preferences, saved state and an Apple recent-document-list entry. Unchecked home data or paths outside the approved scope can suppress Mole’s zap; direct zap can still discard desktop state.
To uninstall without zap, use:
brew uninstall --cask t3-code
Mole checks Homebrew's full removal list and skips --zap when it reaches unchecked data, shared files or anything it cannot verify. It still removes the leftovers you selected. A direct brew uninstall --cask --zap t3-code runs Homebrew’s full zap list without consulting Mole’s checkboxes.
Removing T3 Code does not cancel Claude, Codex or another provider subscription, and does not uninstall those independently installed agents.
What Mole lists
Mole selects the app and exact attributable preference/cache rows by default. ~/.t3/userdata and ~/Library/Application Support/T3 Code (Alpha) are listed for review. With Default remove app data off they start unchecked; with it on, eligible own data can start checked. Inspect and uncheck them to retain desktop state. Project worktrees are not a blanket desktop-uninstall target; the AI page reviews worktrees separately.
What this test covered
On September 25, 2026, the official T3 Code 0.0.42 app was copied from its package and uninstalled with a development build of Mole. Five listed items were moved to the Trash, and no attributed leftovers remained in the recorded window. The small reviewed userdata folder was not recorded as trashed. Active agent tasks, populated worktrees, remote access, an independent service and the published Mole package were not tested.