How to uninstall Cockpit Tools on Mac
Cockpit Tools is an open-source desktop app for managing accounts across AI coding tools such as Codex, Cursor, Windsurf, Antigravity and Grok CLI, from its GitHub project. Its README says the accounts, shared settings, logs, backups and instance configuration it manages are stored in ~/.cockpit_tools, and that these include login tokens, so treat that folder as a secret. When you switch accounts it also writes the chosen login into the other tools' own folders, such as ~/.codex, ~/.grok and ~/.zcode/v2. Decide what to keep before you remove anything. This guide covers the Apple silicon disk image from the project's GitHub releases; there is no Homebrew cask for it.
Quit and remove the app
- Note which accounts you will want again, and delete the accounts you no longer need inside Cockpit Tools. The README suggests deleting accounts and quitting the app on a shared computer. If you want to keep the whole set, copy
~/.cockpit_toolsto a safe place; an export from the app is not a full login backup, since the README says the Grok CLI export leaves tokens out and cannot restore a login. - Quit Cockpit Tools. The README says its close button can minimize it to the tray, so quit it from its tray or menu bar icon, or press Command + Q while its window is in front. In the test the app ran 5 processes, which Mole's Status page groups into one Cockpit Tools row.
- Open Finder, go to Applications and drag Cockpit Tools to the Trash.
The test recorded no login item or launch agent for Cockpit Tools.
Where the data lives
Press Shift + Command + G in Finder to open each path. Skip any path that is not on your Mac.
| Location | What it holds | What to do |
|---|---|---|
~/.cockpit_tools |
Per the README, accounts for every platform, shared settings, logs, backups and instance configs, with managed instances under instances/<platform>. A custom folder set through COCKPIT_TOOLS_DATA_DIR replaces it |
Copy what you need first, then remove. Mole does not list it. |
~/.antigravity_cockpit |
The folder's older name. The README says existing installs get a link from the old name to the new folder, so it may be a link or an older real folder | Handle it with ~/.cockpit_tools. Mole does not list it. |
~/.codex, ~/.grok, ~/.zcode/v2 |
The login of Codex, Grok CLI and ZCode themselves, which Cockpit Tools rewrites when you switch accounts | Keep. They belong to those tools, and removing Cockpit Tools leaves whichever account you switched to last signed in there. |
The login keychain item with service gemini and account antigravity |
Antigravity's own sign-in, which Cockpit Tools overwrites when you switch an Antigravity account, per its source | Keep. It belongs to Antigravity and holds the account you switched to last. Mole does not list keychain items. |
~/Library/Application Support/cockpit-tools |
8 KB in the test | Remove. Mole lists it for review and selects it by default. |
~/Library/Caches/com.jlcodes.cockpit-tools |
Cache, 324 KB in the test | Remove. Selected by default. |
~/Library/WebKit/com.jlcodes.cockpit-tools |
Web view storage, 946 KB in the test | Remove. Selected by default. |
Temporary cache folders named com.jlcodes.cockpit-tools inside the folders getconf DARWIN_USER_CACHE_DIR and getconf DARWIN_USER_TEMP_DIR print |
Empty in the test | Remove with the app. Selected by default. |
Check the result
pgrep -il cockpit-tools
lsof -nP -iTCP:19528 -sTCP:LISTEN
ls -d "$HOME/.cockpit_tools" "$HOME/.antigravity_cockpit" "$HOME/Library/Application Support/cockpit-tools" "$HOME/Library/WebKit/com.jlcodes.cockpit-tools"
- No output from
pgrepmeans Cockpit Tools is not running. A printed line is a process still alive; quit it from its tray or menu bar icon or restart the Mac once. - No output from
lsofmeans nothing listens on port 19528, which the README gives as the default for its local WebSocket service; the test did not record this port. A printed line names the process holding it, which can be another program if you changed the setting. - A path printed by
lsstill exists. A surviving~/.cockpit_toolsis expected if you kept your accounts.No such file or directorymeans that path is gone.
Account and subscription
Cockpit Tools has no account of its own; the README says it does not need a separate platform account. Removing it does not sign you out of Codex, Cursor or the other services, and it does not cancel anything with them. Their sessions stay in each tool's own folders as described above.
What Mole lists
Mole selects the app, the cache, the web view storage and both temporary cache folders. It lists ~/Library/Application Support/cockpit-tools for review and selects it by default. Mole does not list ~/.cockpit_tools or the other tools' folders, so the accounts and tokens in them stay until you handle them yourself. Before removing, Mole asks Cockpit Tools to quit.
What this test covered
On November 9, 2026, the test downloaded the Apple silicon disk image 1.3.80 from the project's GitHub release, whose sha256 matched the official release, copied the app to Applications, opened it once and quit it. It was removed with a source-built, re-signed Debug build of Mole with every review row ticked; Mole's notarized release build was not used. Mole moved 5 rows and the app to the Trash with no failures, and nothing attributed to Cockpit Tools was left. The test did not check whether ~/.cockpit_tools existed after the first launch. Status showed one Cockpit Tools row with 5 processes, and Mole found no update channel, so no update was run. No account was added, so switching accounts, managed instances, the local WebSocket service and the other tools' login files were not tested.
