Unregister first. Remove files second.
Important: server registration, the installed binary, local state, plugin profiles, rendered hooks, and host transcripts are separate surfaces. Removing one does not prove the others are gone.
1. Unregister the server
While programmer.exe is still available, run the exact target you installed:
programmer.exe uninstall --target claude-desktop programmer.exe uninstall --target claude-code programmer.exe uninstall --target lm-studio # Or unregister the three explicit CLI targets: programmer.exe uninstall --target all
The current CLI does not accept cowork or a generic host target. For a manually configured host, remove only the programmer MCP entry using that host's documented configuration flow. Restart each affected host and confirm the Programmer tools no longer appear.
2. Remove the program
- v2 release-candidate ZIP: after unregistering and backing up anything you need, remove the extracted Programmer folder.
- Future installers: if a later release provides one, follow that exact release's uninstall instructions rather than assuming the RC ZIP procedure applies.
3. Decide what to do with local state
Inspect the .programmer folder beside a portable executable before removing it. It may contain session, watcher, recovery, or audit state you want to retain. Tools may also have created checkpoints, logs, downloads, repositories, or output in paths you selected. Delete those only after you identify the exact paths and decide they are no longer needed.
4. Remove optional plugin and hook configuration separately
The programmer and programmer-skills profiles are separate from the server registration. Remove the installed profile through the host's plugin flow. If you previously rendered and merged opt-in hook fragments, review the host's hook configuration and remove only the Programmer-owned entries. Example files in the repository are inert and do not need runtime cleanup.
5. Check host-owned records
Your AI host may retain transcripts, tool-call logs, approvals, or cached configuration under its own retention controls. Programmer's uninstall command does not erase those records. Follow the host's privacy and deletion controls if you want them removed.