How to uninstall QoderWork on Mac
QoderWork keeps your conversations and scheduled tasks on your Mac, in a database under ~/Library/Application Support/QoderWork/data, and its skills, plugins and agent sessions in ~/.qoderwork. Removing the app leaves both unless you delete them. If you are moving to the newer Qoder app, its data import copies QoderWork's conversations, scheduled tasks, memories, user-level skills, MCP connectors and plugins from the same Mac, so run it before you remove anything. Files QoderWork created for you, such as documents on your Desktop, are yours and stay where they are. This guide covers QoderWork downloaded from qoder.com, bundle ID com.qoder.work.
Turn off the login item and quit every QoderWork process
QoderWork adds itself to the apps that open at login, so its scheduled tasks can run whenever you are signed in to your Mac.
- Open System Settings › General › Login Items & Extensions and remove QoderWork from the list of apps that open at login.
- Quit QoderWork from its app menu or with Command-Q.
- Closing the window is not always the end of it. In this test a background worker for the browser extension relay,
browser-extension-relay-worker.js, kept running from QoderWork's own executable after the window was gone, and Mole reported the app as still running and skipped it. Check for it:
pgrep -fl QoderWork
No output means this full-command search found no match, not that every helper has exited. A match can also be another command merely containing “QoderWork”. Before stopping it, open that process in Activity Monitor and check its executable path belongs inside the QoderWork.app you are removing. Save its work, then quit the confirmed app-owned process, or send that verified process a termination signal:
kill PID
Replace PID with the number at the start of the confirmed line, then repeat the check until every process confirmed to belong to the QoderWork.app being removed has exited. Identify other matches without terminating them. "No such process" means that PID had already exited.
If you added the QoderWork browser extension to Chrome, remove it from the browser's extensions page as well. Uninstalling the app does not touch your browser.
Move QoderWork to Trash
Open the Applications folder in Finder and move QoderWork to Trash.
Where QoderWork 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/QoderWork |
data/agents.db with your conversations and scheduled tasks, sign-in state and browser partitions (16 MB in this test) |
Back up or import what you want to keep, then remove it |
~/.qoderwork |
Agent session transcripts, built-in and installed skills, plugins, the computer-use component and DingTalk connector binaries for several platforms (139 MB in this test) | Keep any skills you made yourself, then remove it |
~/.qoder, ~/.qoder-cli, ~/.qodersec |
Shared with Qoder IDE, the Qoder CLI and the newer Qoder app | Keep them while any of those is installed |
~/.dws |
The DingTalk connector's folder; any tool that connects to DingTalk can write to it | Keep it if another app uses the DingTalk connector |
~/Library/Logs/QoderWork |
Logs | Remove with the app |
~/Library/Preferences/com.qoder.work.plist |
Preferences | Remove with the app |
These descriptions come from what this test observed on disk; Qoder's documentation does not list QoderWork's local paths.
Check the result
pgrep -fl QoderWork
ls -d /Applications/QoderWork.app
ls -d "$HOME/Library/Application Support/QoderWork" ~/.qoderwork ~/.qoder
- No output from
pgrepmeans no command matched this search. For every match, verify the executable path before treating it as QoderWork or stopping it. ls -d /Applications/QoderWork.appprinting the path means the app is still there, often because a running process stopped the removal.- The last
ls -dprints each folder that still exists and reports "No such file or directory" for the rest. A surviving~/.qoderis expected while Qoder IDE or another Qoder product is installed.
Also check System Settings › General › Login Items & Extensions once more; QoderWork should no longer be listed. No Homebrew cask for QoderWork was found. Removing the app does not cancel a Qoder subscription or delete your account. For how to find what keeps running after an uninstall, see App Still Running After Uninstall on Mac?.
What Mole lists
When you remove QoderWork with Mole:
~/Library/Preferences/com.qoder.work.plist,~/Library/Logs/QoderWork, temporary caches and the recent-documents entry are selected by default, and so are the rebuildable caches and logs inside~/Library/Application Support/QoderWork(Cache,Code Cache,Crashpad,blob_storage,logs).~/Library/Application Support/QoderWorkitself, with your conversations and scheduled tasks, stays unticked with “Remove data and settings with apps” off; turning it on can select eligible reviewed app data.~/.qoderworkstays unticked with “Remove data and settings with apps” off; turning it on can select eligible reviewed app data.~/.qoder,~/.qoder-cliand~/.qodersecare listed only while Qoder IDE is not installed. With “Remove data and settings with apps” off, these shared rows stay unticked; eligible data can be selected with it on. Mole does not check for the Qoder CLI or the newer Qoder app, so uncheck every shared folder either still uses. Protected agent archives still need individual review or remain locked.~/.dwsis not listed.- If a QoderWork process is still running, Mole reports the app as running and skips it; end the process and remove it again.
What this test covered
QoderWork 0.9.18 was downloaded from qoder.com, copied into Applications and signed in on September 28, 2026. It ran a few tasks, created a text file on the Desktop, installed skills and got a scheduled task. It added itself to the login items. On September 29 it was quit and removed with a development build of Mole with every row ticked, in a run with other AI apps. Before removal Mole's Status page showed it as one row of 13 processes using 996 MB. The first attempt was skipped because the browser extension relay worker was still running after the app was confirmed quit; after that process was ended, the second attempt moved the app and the selected rows to the Trash, and the login item was gone. ~/.qoderwork (139 MB) and the folders shared with Qoder IDE were not in Mole's list in that run, and Mole lists them now. The file QoderWork created on the Desktop was left alone. The browser extension, data import into the newer Qoder app and signing out were not tested.
