How to uninstall CodeBuddy CN on Mac
CodeBuddy CN is the mainland edition of Tencent's AI code editor. Its extensions live in ~/.codebuddycn (315 MB in this test, most of it extensions imported from VS Code on first launch), the editor's own data lives in ~/Library/Application Support/CodeBuddy CN, and ~/.codebuddy holds skills, plugins and MCP settings that Tencent's WorkBuddy also reads. Removing the app leaves all three, so decide on each before you delete anything. This guide covers the download from codebuddy.cn and the Homebrew cask codebuddy-cn; the international CodeBuddy is a separate app.
Sign out and quit
- If you are signed in, sign out from CodeBuddy CN's account menu. This test did not check what signing out clears.
- Quit CodeBuddy CN with Command-Q. It ran 41 processes in this test, so search for CodeBuddy in Activity Monitor and wait until they have exited.
- CodeBuddy CN did not add a login item in this test. If System Settings › General › Login Items & Extensions still shows a CodeBuddy entry, turn it off.
Move the app to Trash
Open the Applications folder in Finder and move CodeBuddy CN to the Trash.
Where CodeBuddy CN keeps its files
In Finder, press Shift + Command + G and check each location. Skip the ones that do not exist.
| Location | What it holds | What to do |
|---|---|---|
~/Library/Application Support/CodeBuddy CN |
Editor data, the extension download cache and logs (72 MB in this test) | Back up anything you want to keep, then remove it |
~/.codebuddycn |
Installed extensions, under extensions |
Remove it unless you plan to reinstall and want the same extensions |
~/.codebuddy |
Skills, plugins, mcp.json, settings and history for CodeBuddy tools; WorkBuddy uses the same folder |
Keep it while WorkBuddy or the CodeBuddy command-line tool is installed; otherwise look inside, back up what you wrote, then remove it |
~/CodeBuddy |
A visible folder created on first launch, empty in this test | Look inside and keep anything you saved there |
~/Library/Application Support/CodeBuddyExtension |
Caches, logs and sign-in data; WorkBuddy's FAQ also points to this folder for its own sign-in | Keep it while WorkBuddy is installed; otherwise remove it |
~/Library/Application Support/com.tencent.codebuddycn, ~/Library/Application Support/com.tencent.codebuddycn.helper |
Small support files | Remove with the app |
~/Library/Caches/com.tencent.codebuddycn, ~/Library/Caches/com.tencent.codebuddycn.helper, ~/Library/Caches/com.tencent.codebuddycn.ShipIt |
Caches, including the updater's | Remove with the app |
~/Library/HTTPStorages/com.tencent.codebuddycn, ~/Library/HTTPStorages/com.tencent.codebuddycn.helper, ~/Library/HTTPStorages/com.tencent.codebuddycn.binarycookies |
Web storage and cookies | Remove with the app |
~/Library/Preferences/com.tencent.codebuddycn.plist, ~/Library/Preferences/com.tencent.codebuddycn.helper.plist |
Preferences | Remove with the app |
Tencent's CodeBuddy IDE FAQ names the extension cache under Application Support/CodeBuddy CN and the extensions under .codebuddycn/extensions, and the .codebuddy directory reference describes ~/.codebuddy as user-level configuration, history and runtime data that affects all projects. That WorkBuddy shares ~/.codebuddy, and the ~/CodeBuddy folder, come from this test, not from Tencent's documentation.
Remove the shell line CodeBuddy CN added
On first launch CodeBuddy CN appended two lines to ~/.zshrc: a comment reading # Added by CodeBuddy CN - shell command, followed by a line that adds the bin folder inside ~/.codebuddy to your PATH. Neither Mole nor removing the app touches that file. To find the lines:
grep -n "CodeBuddy" ~/.zshrc
No output means the lines are not there. If they are, open ~/.zshrc in a text editor, delete the comment and the export PATH line right below it, save, and open a new Terminal window. Leave the line alone if you still use WorkBuddy or the CodeBuddy command-line tool and they rely on it.
Check the result
pgrep -il codebuddy
ls -d "/Applications/CodeBuddy CN.app"
ls -d "$HOME/Library/Application Support/CodeBuddy CN" ~/.codebuddycn ~/.codebuddy ~/CodeBuddy
- No output from
pgrepmeans no CodeBuddy process is running. A listed process means CodeBuddy CN, or WorkBuddy if it is installed, is still open; check the name before quitting anything. ls -don the app printing its path means the app is still in Applications.- The last command prints each folder that still exists and reports "No such file or directory" for the rest. A surviving
~/.codebuddyis expected while WorkBuddy is installed.
If you installed it with Homebrew
The codebuddy-cn cask's zap list trashes ~/.codebuddycn, ~/Library/Application Support/CodeBuddy CN, ~/Library/Application Support/CodeBuddyExtension, everything under ~/Library/Application Support whose name starts with com.tencent.codebuddycn, both caches, web storage, both preferences files and CodeBuddy CN's entry in the recent-documents list. Running brew uninstall --cask --zap codebuddy-cn yourself moves all of them to the Trash whatever you ticked in Mole, including CodeBuddyExtension that WorkBuddy may still use. Homebrew CodeBuddy CN cask
To keep your settings and extensions, remove only the app:
brew uninstall --cask codebuddy-cn
The zap list does not include ~/.codebuddy or ~/CodeBuddy. Mole never adds --zap for this cask, because ~/.codebuddycn sits outside ~/Library; it removes the app and the rows you selected instead.
Removing CodeBuddy CN does not cancel a paid plan or delete your Tencent account.
What Mole lists
When you remove CodeBuddy CN with Mole:
- Preferences, caches (including the updater's), web storage and cookies,
Application Support/com.tencent.codebuddycn, the recent-documents entry and temporary caches filed undercom.tencent.codebuddycnare selected by default. - The Chromium caches and logs inside
Application Support/CodeBuddy CN(Cache,Code Cache,GPUCache,DawnGraphiteCache,DawnWebGPUCache,blob_storage,logs) and insideApplication Support/CodeBuddyExtension(Cache,logs) are selected by default. ~/Library/Application Support/CodeBuddy CN,~/Library/Application Support/CodeBuddyExtension, the helper's Application Support and web storage folders,~/.codebuddycnand~/CodeBuddyare listed for review. With Default remove app data off they start unchecked; with it on, eligible rows can start checked. Back up settings and output before removal, and uncheckCodeBuddyExtensionwhile WorkBuddy still uses it, including its selected cache and log rows.~/.codebuddyis listed for review only when WorkBuddy is not installed. It can start checked with Default remove app data on; uncheck it if you still use the CodeBuddy command-line tool or want its settings and history.- The line in
~/.zshrcis not edited.
What this test covered
CodeBuddy CN 4.12.1 was downloaded from codebuddy.cn, signed in and used for a chat and an Agent-mode task on September 28, 2026, then quit and removed on September 29 with a development build of Mole, in a run with other AI apps. Before removal Mole's Status page showed it as one row of 41 processes using 4.49 GB of memory. It added no login item. With every row ticked, the app and its support data, including ~/.codebuddycn, went to the Trash. At that point Mole did not list ~/.codebuddy or ~/CodeBuddy; both are listed now, as described above. An earlier check of version 4.12.0 also removed the app, its support data and ~/.codebuddycn, and found a crash reporter and a screenshot listener process still running afterwards. Signing out, the Homebrew cask, the CodeBuddy command-line tool and account deletion were not tested.
