How to uninstall Cotypist on Mac
Cotypist is an on-device autocomplete app for Apple silicon Macs from cotypist.app that suggests your next words in other apps. Per its uninstall page, its settings, local data and downloaded models sit in ~/Library/Application Support/app.cotypist.Cotypist, with the models in a Models subfolder, and more data in ~/Library/Caches/app.cotypist.Cotypist. Its privacy page describes an optional, off-by-default recording of your writing, stored encrypted on your Mac and copied to your own iCloud if you turn on sync. If you used that, delete the recorded writing in Cotypist's settings before you remove the app, because the vendor says that deletion also reaches iCloud and your other Macs. This guide covers the Apple silicon disk image from cotypist.app and the Homebrew cask cotypist.
Quit and remove the app
- If you turned on recording or iCloud sync, delete the recorded writing in Cotypist's settings first.
- Open Cotypist's menu bar icon and choose Quit Cotypist.
- Open Finder, go to Applications and drag Cotypist to the Trash.
- If you accepted the setup offer to turn off macOS inline predictions, open System Settings › Keyboard, click Edit… next to Input Sources under Text Input and turn Show inline predictive text back on, as the vendor's uninstall page describes.
- You can also remove the permissions you granted, such as Accessibility (named Device Control and Data Access on newer macOS) and Screen Recording, under System Settings › Privacy & Security.
Mole's log for the test shows it removing one Cotypist login item through System Events; check System Settings › General › Login Items & Extensions if you want to confirm it is gone.
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 |
|---|---|---|
~/Library/Application Support/app.cotypist.Cotypist |
Settings, local data and downloaded models, 365 KB in the test | Remove; models download again if you reinstall. Selected by default. |
~/Library/Caches/app.cotypist.Cotypist |
Cache, 225 KB in the test | Remove. Mole lists it for review and selects it by default. |
~/Library/Caches/SentryCrash/Cotypist |
Crash report cache, 4 KB in the test | Remove this folder only; SentryCrash is shared with other apps that use the same crash reporter. Selected by default. |
~/Library/Preferences/app.cotypist.Cotypist.plist |
Preferences | Remove. Selected by default. |
~/Library/HTTPStorages/app.cotypist.Cotypist, ~/Library/HTTPStorages/app.cotypist.Cotypist.binarycookies |
Network storage and cookies | Remove. Selected by default. |
A temporary cache folder named app.cotypist.Cotypist inside the folder getconf DARWIN_USER_CACHE_DIR prints |
Empty in the test | Remove with the app. Selected by default. |
~/Library/Application Support/com.apple.sharedfilelist/com.apple.LSSharedFileList.ApplicationRecentDocuments/app.cotypist.cotypist.sfl4 |
The app's recent-documents list | Safe to leave. Mole may list the app's own list; the test build could not read this folder without Full Disk Access and left the file. Leave the other files in com.apple.sharedfilelist alone. |
Check the result
pgrep -il cotypist
ls -d "$HOME/Library/Application Support/app.cotypist.Cotypist" "$HOME/Library/Caches/app.cotypist.Cotypist" "$HOME/Library/Preferences/app.cotypist.Cotypist.plist"
launchctl list | grep -i cotypist
- No output from
pgrepmeans Cotypist is not running. A printed line is a process still alive; quit it from its menu bar icon or restart the Mac once. - A path printed by
lsstill exists.No such file or directorymeans that path is gone. - No output from
launchctlmeans no Cotypist job is loaded for your user. A line means a background item is still registered; turn it off in Login Items & Extensions.
If you installed it with Homebrew
brew uninstall --cask cotypist
The cask has no uninstall step, so this removes the app and leaves its data. Its zap list covers ~/Library/Application Support/app.cotypist.Cotypist, the cache, HTTPStorages and preferences entries above and the recent-documents list. Running brew uninstall --cask --zap cotypist deletes those, including downloaded models and anything recorded there, and does not read Mole's checkboxes. Mole adds --zap only when its whole removal scope passes its zap gate; unchecked or shared paths, paths outside the reviewed boundary and any matching path it did not list suppress it, and Mole then removes the selected rows itself.
Account and subscription
Uninstalling does not cancel a subscription. The vendor's cancel page says to use the link in the email you got when you subscribed, or request it again from the subscription activation page. The free plan and the 30-day Pro trial need no account, according to the site.
What Mole lists
Mole selects the app, Application Support/app.cotypist.Cotypist, the preferences file, both HTTPStorages entries, the SentryCrash/Cotypist cache and the temporary cache folder. It lists ~/Library/Caches/app.cotypist.Cotypist for review and selects it by default. Before removing, Mole asks Cotypist to quit, and it removes Cotypist's login item. The recent-documents list is only found when Mole can read that folder, which needs Full Disk Access.
What this test covered
On November 9, 2026, the test downloaded the Apple silicon disk image 2026.5.2 from cotypist.app, whose sha256 matched the Homebrew cask, copied the app to Applications without running brew install, 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 7 rows and the app to the Trash with no failures, and removed one Cotypist login item through System Events. The only item left was the recent-documents file, because that build ran without Full Disk Access and could not read its folder. Status showed one Cotypist row with 2 processes, and Mole detected a Sparkle update feed; no update was run. No account was signed in and no subscription was started. Setup permissions, writing recording, iCloud sync and a Homebrew-managed uninstall were not tested.
