How To Uninstall ClawdBot / MoltBot on Windows (Working Guide 2026)
Learn how to completely uninstall ClawdBot and MoltBot from Windows by removing services, deleting configuration files, and verifying complete system cleanup.
This page may contain affiliate links. If you purchase through these links, we may earn a commission at no extra cost to you. Full disclosure.
Introduction
Introduction
This tutorial walks through the complete process of uninstalling ClawdBot (also known as MoltBot) from your Windows system. You'll stop background services, remove gateway processes, delete configuration files, and verify that the application has been completely removed. By the end of this guide, your Windows device will be completely free of ClawdBot and all its associated files.
Open PowerShell as Administrator
Watch from 0:06- Press the Windows key and type "PowerShell" into the search bar.
- This step is covered at the beginning of the video at [0:06].
Press the Windows key and type "PowerShell" into the search bar. Right-click on Windows PowerShell and select Run as administrator to ensure you have the necessary permissions to execute all uninstall commands.
This step is covered at the beginning of the video at 0:06. PowerShell provides the command-line interface needed to execute the ClawdBot removal commands. Verify that you see the administrator indicator in the PowerShell window title bar before proceeding.
Execute the One-Step Uninstall Command
Watch from 0:11- Run the comprehensive uninstall command that removes most ClawdBot components in a single operation.
- This command is demonstrated in the video at [0:11] through [0:18].
- After executing this command, you should see output indicating that various ClawdBot components are being uninstalled.
Run the comprehensive uninstall command that removes most ClawdBot components in a single operation. Type the following command into your PowerShell window:
Claudbot uninstall --all --yes
This command is demonstrated in the video at [0:11] through [0:18]. The --all flag ensures that all ClawdBot components are targeted for removal. The --yes flag automatically confirms all prompts, allowing the uninstallation to proceed without manual confirmation at each step.
After executing this command, you should see output indicating that various ClawdBot components are being uninstalled. The process may take several seconds to complete. Wait for the command prompt to return before proceeding.
Stop the ClawdBot Gateway Background Process
Watch from 0:22- Even after running the main uninstall command, the ClawdBot gateway service may still be running in the background.
- This step is covered in the video at [0:22] through [0:23].
- You should see a confirmation message indicating that the gateway service has been stopped successfully.
Even after running the main uninstall command, the ClawdBot gateway service may still be running in the background. Enter the following command in your PowerShell window:
Claudbot gateway stop
This step is covered in the video at 0:22 through 0:23. The gateway process handles background synchronization and communication tasks. Stopping it ensures that no ClawdBot processes are actively running while you complete the removal.
You should see a confirmation message indicating that the gateway service has been stopped successfully. If you receive an error stating the service is already stopped, that's perfectly fine—proceed to the next step.
Remove the Gateway Service from Your System
Watch from 0:27- Stopping the gateway process only halts its current execution but doesn't remove it from your system.
- This command is shown in the video at [0:27] through [0:29].
- After executing this command, the gateway service will be completely removed from your Windows services list.
Stopping the gateway process only halts its current execution but doesn't remove it from your system. Run the following command to completely uninstall the gateway service:
clawbot gateway uninstall
This command is shown in the video at 0:27 through 0:29. The gateway uninstall command removes the service registration from Windows, preventing the gateway from starting automatically when your computer boots up.
After executing this command, the gateway service will be completely removed from your Windows services list. Verify this by opening the Services management console (services.msc) and searching for any ClawdBot-related entries, which should no longer appear.
Delete Hidden Configuration Data
Watch from 0:36- ClawdBot stores configuration settings in a hidden directory that the standard uninstall process may not remove.
- This step is covered in the video at [0:36] through [0:45].
- Be careful when using the `rm -rf` command as it permanently deletes files without sending them to the Recycle Bin.
ClawdBot stores configuration settings in a hidden directory that the standard uninstall process may not remove. Manually delete this directory using the following command:
rm -rf ~/.cloudbot
This step is covered in the video at [0:36] through [0:45]. The tilde (~) represents your user home directory, and the dot prefix (.) indicates a hidden folder. The -rf flags force recursive deletion of the directory and all its contents.
Be careful when using the rm -rf command as it permanently deletes files without sending them to the Recycle Bin. After running this command, your ClawdBot configuration data, preferences, and cached settings will be completely removed with no confirmation prompt.
Delete Your ClawdBot Workspace Files
Watch from 0:49- In addition to configuration data, ClawdBot maintains a workspace directory where project files are stored.
- This command is demonstrated in the video at [0:49] through [0:53].
- After executing this command, check your user directory to confirm that the "cloud" folder has been removed.
In addition to configuration data, ClawdBot maintains a workspace directory where project files are stored. Remove this directory with the following command:
rm -rf ~/cloud
This command is demonstrated in the video at 0:49 through 0:53. The workspace directory typically contains project files, temporary data, and other working files created by ClawdBot. Deleting this directory ensures a complete cleanup of all ClawdBot-related data.
After executing this command, check your user directory to confirm that the "cloud" folder has been removed. If you had important project files in this directory that you want to keep, back them up before running this deletion command.
Uninstall the Package Using npm
Watch from 0:55- If you originally installed ClawdBot using npm (Node Package Manager), remove the package from your npm global packages.
- This step is shown in the video at [0:55] through [1:02].
- After running this command, npm will uninstall the ClawdBot package and display a list of removed components.
If you originally installed ClawdBot using npm (Node Package Manager), remove the package from your npm global packages. Run the following command:
npm rm -g claudbot
This step is shown in the video at [0:55] through [1:02]. The rm command removes the package, and the -g flag specifies that you're removing a globally installed package. This ensures that the ClawdBot command-line tools are removed from your system PATH.
After running this command, npm will uninstall the ClawdBot package and display a list of removed components. The process should complete within a few seconds. If you receive an error indicating that the package is not found, it may have already been removed or you might have installed it using a different package manager.
Uninstall the Package Using PNPM (Alternative Method)
Watch from 1:02- If you used PNPM instead of npm to install ClawdBot, use PNPM's removal command instead.
- This alternative method is covered in the video at [1:02] through [1:07].
- Similar to the npm removal process, PNPM will display confirmation that the package has been removed.
If you used PNPM instead of npm to install ClawdBot, use PNPM's removal command instead. Execute the following command:
pnpm remove -g claudbot
This alternative method is covered in the video at 1:02 through 1:07. PNPM is an alternative package manager that uses a different storage mechanism than npm. Using the correct package manager for removal ensures that all package links and dependencies are properly cleaned up.
Similar to the npm removal process, PNPM will display confirmation that the package has been removed. If you're unsure which package manager you used originally, try both commands—the one that doesn't find the package will simply report that it's not installed.
Verify Complete Removal
Watch from 1:07- Confirm that ClawdBot has been completely removed from your system by attempting to run the ClawdBot version command:
- This verification step is shown in the video at [1:07] through [1:13].
- If you still see a version number displayed, some components of ClawdBot remain installed.
Confirm that ClawdBot has been completely removed from your system by attempting to run the ClawdBot version command:
cloudbot --version
This verification step is shown in the video at 1:07 through 1:13. If ClawdBot has been successfully uninstalled, you should see an error message stating "command not found" or "'cloudbot' is not recognized as an internal or external command." This confirms that the ClawdBot executable is no longer available in your system PATH.
If you still see a version number displayed, some components of ClawdBot remain installed. Review the previous steps to ensure all commands were executed successfully. You may also want to restart your PowerShell session or reboot your computer to clear any cached PATH variables.
Prompt Library
Copy-paste these prompts directly into the chatbot of your choice for best results. Each prompt has been tested and optimized for this workflow.
Troubleshooting & Common Errors
Running into issues? Here are the most common problems and how to fix them.
Expert Tips
Continue Learning
Explore More Tools
This tutorial was created by Joshua Kishaba and produced using AI-assisted editorial tools. All recommendations reflect genuine editorial opinion based on hands-on testing. This page may contain affiliate links — see our full disclosure.