How to Uninstall OpenClaw Completely: macOS, Windows & Linux

Quick Uninstall Command

If you want the fastest path to a clean removal, run this single command:

openclaw uninstall --all --yes --non-interactive

This stops the running agent, removes the service registration, deletes the state directory, and cleans up configuration files. Follow it with the NPM uninstall and OAuth token revocation steps below to complete the process.

If you want more control over what gets removed, or if the command fails (common on older installations from the ClawDBot era), follow the manual steps for your platform below.

What the Uninstall Command Does

The openclaw uninstall --all --yes --non-interactive command performs four actions in sequence:

1. Stops the gateway — sends a graceful shutdown signal to the running OpenClaw process, waiting up to 30 seconds for it to complete any in-progress tasks before force-killing
2. Removes the service registration — deletes the platform-specific service file that keeps OpenClaw running after reboot:
   • macOS: LaunchAgent plist at ~/Library/LaunchAgents/com.openclaw.agent.plist
   • Linux: systemd unit at ~/.config/systemd/user/openclaw.service
   • Windows: Scheduled Task named "OpenClaw"
3. Deletes the state directory — removes ~/.openclaw/state which contains conversation history, memory files, and runtime state
4. Removes CLI from PATH — cleans up any PATH modifications that were added during installation

What the command does not do:

• It does not uninstall the npm package itself — you need to run npm rm -g openclaw separately
• It does not revoke OAuth tokens from external services — these persist on Google, Slack, and Discord servers
• It does not remove legacy directories from the ClawDBot or MOLTBot eras
• It does not remove Docker containers or images

NPM / pnpm / Bun Uninstall

After running the OpenClaw uninstall command, remove the CLI binary from your system:

# If you installed with npm
npm rm -g openclaw

# If you installed with pnpm
pnpm rm -g openclaw

# If you installed with bun
bun rm -g openclaw

Verify the CLI is removed:

which openclaw
# Should return nothing or "openclaw not found"

Manual Cleanup: macOS

If the automated uninstall did not fully clean up, or if you need to remove files manually:

Step 1: Stop the Agent

# Stop via OpenClaw CLI (if still installed)
openclaw stop

# Or stop via launchctl
launchctl unload ~/Library/LaunchAgents/com.openclaw.agent.plist

Step 2: Remove the LaunchAgent

rm -f ~/Library/LaunchAgents/com.openclaw.agent.plist

Step 3: Remove Application Support Data

rm -rf ~/Library/Application\ Support/openclaw

Step 4: Remove the Configuration Directory

rm -rf ~/.openclaw

Step 5: Remove Log Files

rm -f ~/Library/Logs/openclaw*.log

Manual Cleanup: Linux

Step 1: Stop the Agent

# Stop via OpenClaw CLI
openclaw stop

# Or stop via systemd
systemctl --user stop openclaw
systemctl --user disable openclaw

Step 2: Remove the systemd Unit

rm -f ~/.config/systemd/user/openclaw.service
systemctl --user daemon-reload

Step 3: Remove Configuration and State

# XDG config directory
rm -rf ~/.config/openclaw

# State directory
rm -rf ~/.openclaw

Step 4: Remove Log Files

# If using journald, logs are cleaned up automatically
# If using file-based logging:
rm -f ~/.local/share/openclaw/logs/*.log
rm -rf ~/.local/share/openclaw

Manual Cleanup: Windows

Step 1: Stop the Agent

# PowerShell — stop via OpenClaw CLI
openclaw stop

# Or find and kill the process
Get-Process -Name "node" | Where-Object { $_.CommandLine -match "openclaw" } | Stop-Process

Step 2: Remove the Scheduled Task

# PowerShell (run as Administrator)
Unregister-ScheduledTask -TaskName "OpenClaw" -Confirm:$false

Step 3: Remove Application Data

# PowerShell
Remove-Item -Recurse -Force "$env:APPDATA\openclaw"
Remove-Item -Recurse -Force "$env:LOCALAPPDATA\openclaw"

Step 4: Remove the Configuration Directory

Remove-Item -Recurse -Force "$env:USERPROFILE\.openclaw"

Revoking OAuth Tokens (Critical)

This is the most commonly missed step, and the most important one for security.

OpenClaw uses long-lived OAuth tokens to connect to Google, Slack, Discord, and other services. These tokens are stored on the provider's servers, not on your machine. Deleting OpenClaw from your computer does not revoke these tokens — they remain valid until you explicitly revoke them.

If you skip this step, the OAuth tokens remain active. If someone gains access to your old backup files or configuration, they could theoretically use those tokens to access your connected accounts.

Google Account

1. Go to Google Account → Security
2. Scroll to "Third-party apps with account access"
3. Click "Manage third-party access"
4. Find "OpenClaw" (or "ClawDBot" / "MOLTBot" if you authorized under an older name)
5. Click "Remove Access"

Slack

1. Go to your Slack workspace settings
2. Navigate to "Manage Apps" or "Authorized Apps"
3. Find the OpenClaw bot integration
4. Click "Revoke" or "Remove"

Discord

1. Go to Discord → User Settings → Authorized Apps
2. Find OpenClaw
3. Click "Deauthorize"

Other Services

If you connected OpenClaw to other services (GitHub, Notion, Linear, etc.), visit each service's settings and revoke the OpenClaw integration. The specific location varies by service, but look for "Authorized Apps," "Connected Apps," or "Third-party integrations" in the security or settings section.

Legacy Directories: ClawDBot and MOLTBot

OpenClaw has been renamed twice since its initial release:

• ClawDBot — the original name, used from November 2025 through late January 2026
• MOLTBot — brief intermediate name, used for a few days in January 2026
• OpenClaw — current name, adopted January 30, 2026

If you installed the agent under either of the previous names, legacy directories may still exist on your machine. The OpenClaw uninstall command does not remove these.

# Check for and remove legacy directories
rm -rf ~/.clawdbot
rm -rf ~/.moltbot

# macOS Application Support
rm -rf ~/Library/Application\ Support/clawdbot
rm -rf ~/Library/Application\ Support/moltbot

# Linux XDG config
rm -rf ~/.config/clawdbot
rm -rf ~/.config/moltbot

# Windows (PowerShell)
Remove-Item -Recurse -Force "$env:APPDATA\clawdbot" -ErrorAction SilentlyContinue
Remove-Item -Recurse -Force "$env:APPDATA\moltbot" -ErrorAction SilentlyContinue

Also check for legacy LaunchAgents or systemd units:

# macOS
rm -f ~/Library/LaunchAgents/com.clawdbot.agent.plist
rm -f ~/Library/LaunchAgents/com.moltbot.agent.plist

# Linux
rm -f ~/.config/systemd/user/clawdbot.service
rm -f ~/.config/systemd/user/moltbot.service
systemctl --user daemon-reload

Docker Cleanup

If you ran OpenClaw in a Docker container, the uninstall command does not handle Docker cleanup. Remove the container and image manually:

# Stop and remove the container
docker stop openclaw
docker rm openclaw

# Remove the image
docker rmi openclaw

If you used a custom container name or a specific image tag:

# List all containers to find the OpenClaw one
docker ps -a | grep openclaw

# List images
docker images | grep openclaw

# Remove by specific ID if needed
docker rm <container-id>
docker rmi <image-id>

If you used Docker Compose:

# From the directory containing docker-compose.yml
docker compose down --rmi all --volumes

Verifying Complete Removal

After completing all steps, verify that OpenClaw is fully removed from your system:

# 1. Check that the CLI is gone
which openclaw
# Expected: no output or "not found"

# 2. Check that no OpenClaw process is running
ps aux | grep openclaw
# Expected: only the grep process itself

# 3. Check that the config directory is gone
ls -la ~/.openclaw
# Expected: "No such file or directory"

# 4. Check that legacy directories are gone
ls -la ~/.clawdbot ~/.moltbot
# Expected: "No such file or directory" for both

# 5. Check that no service is registered
# macOS:
launchctl list | grep openclaw
# Linux:
systemctl --user list-units | grep openclaw
# Expected: no output

If all five checks come back clean, OpenClaw is fully removed from your machine. Remember that OAuth tokens on external services (Google, Slack, Discord) must be revoked separately as described in the OAuth section above.

For the official uninstall documentation, see docs.openclaw.ai/install/uninstall.

Frequently Asked Questions

Will uninstalling OpenClaw delete my conversations?

The uninstall command with the --all flag deletes the state directory (~/.openclaw/state), which contains conversation history, memory files, and agent state. If you want to preserve your conversations, back up the ~/.openclaw/state directory before running the uninstall command. Your SOUL.md persona files and skill files are stored separately and are not deleted by the uninstall command unless they are inside the ~/.openclaw directory.

Do I need to revoke API keys after uninstalling?

Yes, and this is the most commonly missed step. OpenClaw uses long-lived OAuth tokens for Google, Slack, Discord, and other services. These tokens persist on the provider's servers even after you delete OpenClaw from your machine. You must manually revoke them at each provider's security settings page — otherwise the tokens remain valid and could theoretically be used if your backup files are compromised.

Can I reinstall OpenClaw later after uninstalling?

Yes. OpenClaw can be reinstalled at any time with npm install -g openclaw. If you backed up your ~/.openclaw directory before uninstalling, you can restore it to recover your previous configuration, memory, and conversation history. You will need to re-authorize any OAuth integrations (Google, Slack, etc.) since you should have revoked those tokens during uninstall. For a full setup guide, see How to Set Up OpenClaw AI Agent.

Further Reading

• How to Set Up OpenClaw AI Agent — if you decide to reinstall later
• OpenClaw Setup Mistakes and How to Fix Them — common issues that may have led to wanting to uninstall
• Official OpenClaw Uninstall Documentation