How to uninstall Neon Vision Editor on Mac
Before removing Neon Vision Editor, save and copy your text documents, notes and project folders to a separate backup, then open the copy. This guide covers the official Mac download; Homebrew-specific removal is separate below.
The official README documents an optional nve helper linked into ~/bin. If you installed it, inspect ~/bin/nve in Finder and remove that specific link only after confirming it belongs to this app. Keep your document folders and any cloud copies; copy wanted documents outside a sync root before removal and open the backup.
Quit and remove the app
Finish current work and quit Neon Vision Editor. Check Activity Monitor for its process before removing the app in Finder. In Applications, move Neon Vision Editor.app to the Trash; if you keep it elsewhere, use its actual location. Keep the Trash until your backup has been checked. Official documentation
Review local data
The locations below come from the test record or the live cask; their individual treatment is explained below. Open them through Finder’s Go › Go to Folder. Copy wanted contents first; leave them if you want to keep settings or cannot establish ownership. They are optional data removal, not a prerequisite for removing the app.
~/Library/Application Support/NeonVisionEditor~/Library/Group Containers/group.h3p.Neon-Vision-Editor~/Library/Application Scripts/group.h3p.Neon-Vision-Editor
Check the result
This read-only check searches full process command lines, not disk contents.
pgrep -ifl 'Neon Vision Editor'
No output with exit status 1 means no matching command line was found. A printed entry needs inspection in Activity Monitor because names can match unrelated processes. An error is not proof of removal. Also check that the app is absent from its original Finder location; a retained data folder or independent component does not mean the app is still installed.
If you installed it with Homebrew
Use the installed cask receipt and uninstall without zap.
brew uninstall --cask neon-vision-editor
The command removes the cask’s managed application artifacts without running zap. The live cask additionally names these zap targets, which can erase settings, local data or integration files; this is Homebrew’s list, not a vendor data-location claim.
~/Library/Application Scripts/group.h3p.Neon-Vision-Editor~/Library/Application Scripts/h3p.Neon-Vision-Editor*~/Library/Application Support/NeonVisionEditor~/Library/Caches/h3p.Neon-Vision-Editor~/Library/Containers/h3p.Neon-Vision-Editor~/Library/Group Containers/group.h3p.Neon-Vision-Editor~/Library/Logs/NeonVisionEditorUpdater.log~/Library/Preferences/h3p.Neon-Vision-Editor.plist
A direct brew uninstall --cask --zap neon-vision-editor runs its own zap scope without consulting Mole’s checkboxes. Mole uses zap only when the complete scope passes its gate; unchecked or shared paths, paths outside the review boundary, unknown stanzas and unsupported directives suppress it. Selected remnants still use Mole’s deletion path.
What Mole lists
~/Library/Application Support/NeonVisionEditor is an app-data review row, not selected by default. Group-related paths, including ~/Library/Group Containers/group.h3p.Neon-Vision-Editor and ~/Library/Application Scripts/group.h3p.Neon-Vision-Editor, require the App Group ownership checks before removal. A refusal keeps the data; do not bypass it.
These defaults assume “Remove data and settings with apps” is off. Opting in also selects eligible reviewed app data; shared stores and protected data retain individual review or stay locked.
What this test covered
The October 5, 2026 record covers the following test. The official Apple Silicon app was launched on its initial screen and removed using a source-built Mole app. Two group-related paths were retained because the ownership check could not rule out another app using the group, not because of a permission error. The login item disappeared from the refreshed list. Documents and the optional command-line helper were not tested.