Troubleshooting
Solutions to common ClawdBot issues.
Quick Diagnostic: Run
clawdbot status --all to get a full status report.
Installation Issues
"command not found: clawdbot"
Cause: ClawdBot not in your PATH.
Fix:
- Close and reopen terminal
- Check npm prefix:
npm config get prefix - Add to PATH:
export PATH="$(npm config get prefix)/bin:$PATH" - Add that line to your
~/.bashrcor~/.zshrc
Node.js version error
Cause: ClawdBot requires Node.js 22+.
nvm install 22
nvm use 22
node --version
Permission denied (Linux/macOS)
mkdir ~/.npm-global
npm config set prefix '~/.npm-global'
echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.bashrc
source ~/.bashrc
npm install -g clawdbot
Windows: Installation fails
Recommended: Use WSL2 instead of native Windows.
wsl --install
# Restart, then in Ubuntu:
curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -
sudo apt-get install -y nodejs
npm install -g clawdbot
WhatsApp Issues
QR code won't scan / keeps expiring
- Make sure you're using Node.js, not Bun
- QR codes expire quickly—scan within 30 seconds
- Regenerate:
clawdbot channels login - Check internet connection on both computer and phone
WhatsApp disconnects frequently
- Keep phone connected to stable WiFi
- Check WhatsApp → Linked Devices on phone
- Remove old linked devices
- Ensure phone has WhatsApp running in background
ClawdBot not responding to messages
- Check gateway:
clawdbot gateway status - Check if pairing needed:
clawdbot pairing list whatsapp - Approve if needed:
clawdbot pairing approve whatsapp CODE - Check API key has credits
Gateway Issues
Gateway won't start
Check if port is in use:
# macOS/Linux
lsof -i :18789
# Windows
netstat -ano | findstr :18789
Use different port:
clawdbot gateway --port 18790
Gateway crashes on startup
- Run with verbose:
clawdbot gateway --verbose - Check for config issues:
clawdbot config show - Re-run onboarding:
clawdbot onboard
API Issues
"Invalid API key" error
- Verify key at provider's console
- Re-set the key:
clawdbot config set anthropic_api_key "sk-ant-..." - Check for extra spaces in the key
Rate limit errors
- Wait a few minutes and retry
- Upgrade API plan for higher limits
- Use a smaller/faster model
"Insufficient credits" error
Add credits at your provider's billing page:
- Anthropic: console.anthropic.com
- OpenAI: platform.openai.com
Performance Issues
Slow responses
- Check API provider status page
- Use a faster model for simple tasks
- Clear conversation history if very long
High memory usage
- Restart gateway:
clawdbot gateway restart - Update to latest version:
npm update -g clawdbot - Limit connected channels if not needed
Still Stuck?
Generate Debug Report
Run this and share output when seeking help:
clawdbot status --all