How to uninstall CodeEdit on Mac
Save and close open CodeEdit documents, then copy projects from their own folders. If you have custom CodeEdit settings or extensions, inspect its support folder before selecting it for removal. A project opened by CodeEdit remains a separate folder and should not be deleted with editor state.
The recorded test used the official Mac package; the Homebrew route below is separate.
Remove the app
Quit CodeEdit, then move CodeEdit.app from Applications to Trash. Check System Settings › General › Login Items & Extensions only if a CodeEdit helper or extension still appears. Do not move the Open With extension container by guessed name; inspect the exact installed extension.
Review local data
The path below is documented in the current Homebrew cask. In Finder, use Go › Go to Folder to inspect it. Do not remove its parent directory or another product’s data.
| Location | Decision |
|---|---|
~/Library/Application Support/CodeEdit |
Display-name support folder in the cask zap list. Review custom editor state before choosing whether to remove it. |
The tested package uses bundle ID app.codeedit.CodeEdit. Review only files that actually appear on this Mac. A missing path needs no cleanup.
Vendor documentation · Additional vendor instructions
Check what remains
Run these read-only commands after quitting the app:
pgrep -il 'CodeEdit'
ls -d "$HOME/Library/Application Support/CodeEdit"
find "$HOME/Library/Containers" -maxdepth 1 -name "*.CodeEdit.OpenWithCodeEdit" -print
No process output means there is no matching process running now; it does not prove every helper is gone. A listed process needs its owner checked. If ls prints the path, that item remains and needs review. “No such file or directory” means only the support path is absent; a permission error is inconclusive. Each find result is a surviving Open With container; no result means only that this pattern found none. For the Sparkle Downloader failure, use the exact path shown in Mole’s result and inspect it separately, since the downloader can serve other apps.
If you installed it with Homebrew
The current codeedit cask has a zap list covering CodeEdit support data, app scripts, Open With extension container, caches, HTTP storage, preferences and saved state. A direct brew command with --zap applies the cask list without consulting Mole’s checkboxes. After backing up, use this command without --zap:
brew uninstall --cask codeedit
Mole checks each zap path against your selections, other installed apps, and protected locations. An unchecked, shared, or unverifiable path suppresses --zap; selected remnants can still use Mole’s own removal flow. This cask was not the recorded installation channel.
What Mole lists
Mole shows Application Support/CodeEdit as a review row, initially unchecked. Exact app-ID caches and preferences can be selected by default. Extension and downloader containers require their own identity checks; a failed Trash move remains visible as a partial result.
What this test covered
The official CodeEdit 0.3.6 app was removed on September 21, 2026 with review selected. Application Support/CodeEdit went to Trash, while the OpenWithCodeEdit container and Sparkle Downloader hit Trash error 513. Projects and extension customizations were not exercised.