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 WeCom on Mac

    WeCom (企业微信) is a sandboxed Mac app, so what it stores locally, which can include chat data and files received in chats, lives in its container, ~/Library/Containers/com.tencent.WeWorkMac. Mole selects that container by default, like any container named after an app's bundle ID. Before you remove WeCom, check on your phone that the conversations you need are there, and save a copy of any file you still need to a folder outside WeCom. These steps cover WeCom downloaded from work.weixin.qq.com and the Homebrew cask wechatwork; the recorded test used the download from work.weixin.qq.com.

    Save what you need first

    • Open WeCom on your phone and confirm the chats you rely on are available there.
    • For files received in chats, save copies to your own folder and open them to check they work. A file that only exists inside the container goes with it.
    • If your organization manages WeCom, ask its administrator before removing the app from a work Mac; they may have their own rules for chat records.

    Quit WeCom and remove the app

    Quit WeCom from its menu; closing the window leaves it running. Then move 企业微信 from Applications to the Trash.

    WeCom carries helper login items inside the app, IPCHelper and WeWork Helper. In the recorded test they were still listed after removal, pointing at the app in the Trash. Open System Settings › General › Login Items & Extensions and turn off any WeCom entry left there.

    Where WeCom keeps its data

    These are the paths in the Homebrew cask's zap list. Open each with Shift + Command + G in Finder; skip the ones that do not exist.

    Location What it holds What to do
    ~/Library/Containers/com.tencent.WeWorkMac WeCom's sandboxed data, everything the app stores locally Keep until you have saved what you need
    ~/Library/Containers/88L2Q4487U.com.tencent.WeWorkMac and ~/Library/Containers/88L2Q4487U.com.tencent.WeWorkMac.IPCHelper Containers whose names start with a team ID, used by WeCom and its IPC helper Remove with the app
    ~/Library/Application Scripts/com.tencent.WeWorkMac and the matching 88L2Q4487U... folders Script folders macOS creates for sandboxed apps Remove with the app

    The cask also lists variants of these names ending in .dev, Debug and UIDev; skip any that do not exist. On the test Mac WeCom also created group folders under ~/Library/Group Containers whose names start with 88L2Q4487U., a few KB each; the zap list does not name them.

    Check the result

    Run these read-only commands in Terminal after the app is in the Trash:

    pgrep -ilf "企业微信.app"
    ls -d "$HOME/Library/Containers/com.tencent.WeWorkMac"
    
    • No output from pgrep means neither WeCom nor its helpers are running. A listed process means something from the app is still open; quit it before touching the container.
    • ls printing the path means the container, and whatever WeCom kept locally, is still on this Mac. That is the expected result if you unchecked it in Mole to keep it. "No such file or directory" means it is gone.

    If you installed it with Homebrew

    Running brew uninstall --cask --zap wechatwork yourself moves every path in the table above to the Trash, the main container included, so anything WeCom kept only on this Mac goes with it. To keep the container, remove only the app:

    brew uninstall --cask wechatwork
    

    Mole checks the zap list before running it and leaves --zap out if it would reach a row you left unchecked, so unchecking the container in Mole keeps it. Homebrew WeCom cask

    Account

    Removing the Mac app does not affect your WeCom account or your WeCom on other devices. WeCom

    What Mole lists

    For WeCom downloaded from work.weixin.qq.com:

    • ~/Library/Containers/com.tencent.WeWorkMac is selected by default, because it is named after WeCom's bundle ID. Uncheck it if you want to keep WeCom's local data on this Mac.
    • ~/Library/Application Scripts/com.tencent.WeWorkMac is selected by default.
    • Group containers and script folders prefixed with the team ID, such as ~/Library/Group Containers/88L2Q4487U.com.tencent.WeWorkMac, are listed but not selected. The short group folders 88L2Q4487U.WeWorkMac, 88L2Q4487U.WeComAgent and 88L2Q4487U.WeComWeAgent are listed too, but their names do not carry WeCom's bundle ID, so Mole keeps them even when ticked.
    • Login items are not edited; turn them off in System Settings.

    What this test covered

    WeCom was downloaded from work.weixin.qq.com, copied into Applications and uninstalled with Mole Preview 277 on September 19, 2026. One WeCom container could not be moved to the Trash because macOS refused the move, so it stayed on disk. The embedded IPCHelper and WeWork Helper login items were still listed afterwards, pointing at the app in the Trash. On September 26, 2026, WeCom 5.0.11 from the official download was installed again and removed with a development build of Mole with every row ticked: the app, the 3.9 MB container and 10 other listed items went to the Trash, while Mole kept the three short group folders and the 88L2Q4487U.WeWorkMac Application Scripts folder as protected. No WeCom startup item appeared before or after. Chat history, file downloads and the Homebrew cask were not tested.

    Mac running low on space or slowing down? Mole can clean out the junk, remove apps completely and keep macOS in shape.

    Try Mole

    Mole · 鼴

    Cleanup, software, and status for your Mac.

    v1.16.0 (296) · 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.