Quick solutions for common ClawRouter issues.
Need help? Open a Discussion or check existing issues.
# 1. Check your version (should be 0.12+)
cat ~/.openclaw/extensions/clawrouter/package.json | grep version
# 2. Check proxy is running
curl http://localhost:8402/health
# 3. Check wallet (both EVM + Solana addresses and balance)
/wallet
# 4. Watch routing in action
openclaw logs --follow
# Should see: kimi-k2.5 $0.0012 (saved 99%)
# 5. View cost savings
/statsPlugin isn't loaded or outdated. Don't change the model name — blockrun/auto is correct.
Fix: Update to v0.3.21+ which handles both blockrun/auto and auto (OpenClaw strips provider prefix). See How to Update.
Auth profile is missing or wasn't created properly.
Fix: See How to Update — the reinstall script automatically injects the auth profile.
Plugin directory was removed but config still references it. This blocks all OpenClaw commands until fixed.
Fix: See How to Update for complete cleanup steps.
Wallet needs funding. ClawRouter accepts USDC (not SOL or ETH) on either chain.
Fix:
- Find your wallet address: run
/walletin any OpenClaw conversation - Choose your preferred chain and send USDC to that address:
- Base (EVM): Send USDC on Base network to your EVM address (
0x...) - Solana: Send USDC on Solana network to your Solana address (base58)
- Base (EVM): Send USDC on Base network to your EVM address (
- $1–5 is enough for hundreds of requests
- Restart OpenClaw (or wait up to 60s for balance cache to refresh)
This is a false positive. ClawRouter legitimately:
- Reads
BLOCKRUN_WALLET_KEYfrom environment (for authentication) - Sends authenticated requests to BlockRun API (for x402 micropayments)
This pattern triggers OpenClaw's security scanner, but it's the intended behavior — the wallet key is required to sign payment transactions. The code is fully open source and auditable.
OpenClaw's security scanner may flag ClawRouter with:
[env-harvesting] Environment variable access combined with network send
This is a false positive. The scanner's heuristic (env variable + network request = suspicious) flags all payment plugins, but this pattern is inherently required for non-custodial payments.
ClawRouter reads BLOCKRUN_WALLET_KEY to sign x402 payment transactions — this is required and intentional:
- The wallet key is used locally for cryptographic signing (EIP-712)
- The signature is transmitted, not the private key itself
- The key never leaves the machine — only cryptographic proofs are sent
- This is standard x402 payment protocol behavior
- Source code is MIT licensed and fully auditable
See openclaw.security.json for detailed security documentation and this discussion for more context.
As of v0.4.1, ClawRouter automatically detects and reuses an existing proxy on the configured port instead of failing with EADDRINUSE. You should no longer see this error.
If you need to use a different port:
# Set custom port via environment variable
export BLOCKRUN_PROXY_PORT=8403
openclaw gateway restartTo manually check/kill the process:
lsof -i :8402
# Kill the process or restart OpenClawnpx @blockrun/clawrouter@latest
openclaw gateway restartThis installs the latest version and restarts the gateway. Alternatively:
curl -fsSL https://raw.githubusercontent.com/BlockRunAI/ClawRouter/main/scripts/reinstall.sh | bash
openclaw gateway restartopenclaw logs --followYou should see model selection for each request:
[plugins] [SIMPLE] google/gemini-2.5-flash $0.0012 (saved 99%)
[plugins] [MEDIUM] deepseek/deepseek-chat $0.0003 (saved 99%)
[plugins] [REASONING] deepseek/deepseek-reasoner $0.0005 (saved 99%)