Skip to main content
Mole
Features Tested apps Testimonials Pricing FAQ Blog
EnglishEN 简体中文中 繁體中文繁 日本語日 한국어한 FrançaisFR DeutschDE ItalianoIT EspañolES PortuguêsPT
Buy nowBuy Download

    Help, documentation, releases, and articles.

    Home/Apps tested with Mole

    How to uninstall ZCode on Mac

    Save your project files and copy the local ZCode stores before removing the app. Keep code repositories at their actual locations; removing this editor does not cancel a GLM Coding Plan. Official product site

    Back up and remove ZCode

    The local check found settings and sign-in data inside ~/.zcode/v2. Copy the complete ~/.zcode store and ~/Library/Application Support/ZCode to a separate backup, and check the copies before quitting. Then quit ZCode and move ZCode.app from Applications to the Trash.

    Open those exact data paths using Finder’s Go › Go to Folder. Keep them to retain local state; move them only if you have decided to reset it. The separately observed ~/Library/Services/Open in ZCode.workflow is a Finder service: inspect it and remove only that workflow if you no longer need it, keeping the Services parent.

    If you installed it with Homebrew

    brew uninstall --cask zcode
    

    Ordinary removal requests that ZCode quit and removes its managed app. The current cask additionally zaps:

    • ~/Library/Application Support/com.apple.sharedfilelist/com.apple.LSSharedFileList.ApplicationRecentDocuments/dev.zcode.app.sfl*
    • ~/Library/Application Support/ZCode
    • ~/Library/Caches/@zcodedesktop-updater
    • ~/Library/Preferences/dev.zcode.app.plist
    • ~/Library/Services/Open in ZCode.workflow

    It also tries to remove ~/.zcode only if empty. This empty-directory action does not erase a populated store. Direct brew uninstall --cask --zap zcode uses the entire cask scope independently of Mole’s checkboxes; back up and approve every target first. Mole uses zap only when its complete scope passes selection and shared-data checks; unchecked, shared or out-of-boundary paths and unsupported actions suppress zap, while selected remnants use Mole’s removal flow.

    Check the result

    ls -ld "/Applications/ZCode.app"
    ls -ld "$HOME/.zcode" "$HOME/Library/Application Support/ZCode" "$HOME/Library/Services/Open in ZCode.workflow"
    

    Printed entries remain at those paths. No such file or directory means that exact item is absent; permission errors mean its state is unknown. Kept stores are expected when preserving settings. These checks do not inspect project repositories or your online account.

    What Mole lists

    ~/.zcode, ~/Library/Application Support/ZCode and the attributable Finder workflow are listed for review, not selected by default. The app-data option is off by default; enabling Remove data and settings with apps also selects eligible reviewed data, including ZCode’s local store. Shared or protected data still requires its existing individual review or remains locked.

    What this test covered

    The official Mac app was removed on September 21, 2026; its support folder was left unchecked and its home store was then missing from the removal list. A September 25 repeat with the official app selected and removed both local stores. That repeat confirmed the local sign-in location, not account deletion, project recovery or a Homebrew-managed uninstall. The Finder workflow was identified separately; this record does not establish every possible integration was removed.

    If Mac apps leave files behind after uninstalling, try Mole. I've personally tested and inspected 799 Mac apps.

    Try Mole

    Mole · 鼴

    Cleanup, software, and status for your Mac.

    v1.16.0 (301) · Release notes

    Product

    Mac Cleaner App Uninstaller Mac Optimizer Disk Analyzer System Monitor

    Support

    Help Documentation Releases Blog

    Legal

    Terms of Service Privacy Policy Refund Policy

    Resources

    CLI Tool Affiliate Program

    Connect

    Twitter hi@mole.fit

    Mole’s only official website mole.fit · Avoid installers from unknown sources

    The CLI stays free for terminal workflows.