openclaw doctor --fix first โ that handles ~60% of issues automatically. This guide covers the rest.
OpenClaw v2026.3.22 is the biggest release of 2026 โ but it shipped with 12 breaking changes that silently broke thousands of existing setups overnight. If your agent stopped working after updating (or you're too scared to update), this guide covers every issue and exactly how to fix it.
openclaw doctor --fix. This auto-fixes ~60% of migration issues. Then work through this guide for anything still broken.
openclaw doctor --fix
Old config keys (ClawdBot, MoltBot environment variables, legacy channel formats) used to be silently ignored. Now they fail validation and prevent your agent from starting โ often with no clear error message.
Symptoms:
openclaw status shows red with no useful detail# Check which keys are failing
openclaw config validate --verbose
# Let doctor fix what it can
openclaw doctor --fix
# Then restart
openclaw restart
Specific keys to remove from openclaw.json if present:
CLAWDBOT_TOKENMOLTBOT_KEYbrowser.relayBindHostdriver: "extension" (in browser config)Plugin installs now route through ClawHub natively. Skills installed via npm won't appear in openclaw skills list until re-registered.
Symptoms:
openclaw skills list shows fewer skills than expected# Sync all installed skills with ClawHub registry
openclaw skills sync
# Fix Unicode slug issues (known bug)
openclaw skills repair --fix-slugs
# Verify everything registered
openclaw skills list --all
Skills not on ClawHub still work โ they just need manual registration after install:
npm install -g @yourorg/your-skill
openclaw skills register @yourorg/your-skill
The legacy Chrome extension relay path is completely removed. If you used browser automation, your entire browser workflow needs reconfiguration from scratch.
Symptoms:
openclaw browser commands fail# Remove old extension config
openclaw doctor --fix
# Reconfigure for new CDP approach
openclaw browser setup
# Verify
openclaw browser status
The new CDP approach is actually more stable โ no Chrome extension needed. Reconfiguration takes ~10 minutes.
OpenClaw no longer auto-migrates configs older than 2 months. Very old legacy keys that used to be quietly rewritten now fail validation instead.
Who's affected: Anyone running OpenClaw since before January 2026 without a fresh config rebuild.
openclaw config validate --verbose
openclaw doctor --fix
# Manually remove any remaining flagged keys
Several skills commands were renamed. Scripts and automations using old commands will fail silently.
| Old Command | New Command |
|---|---|
openclaw skill install | openclaw skills install |
openclaw skill list | openclaw skills list |
openclaw skill update | openclaw skills update |
openclaw plugin install | openclaw skills install |
Update any scripts using old command names. The new skills (plural) format is permanent.
openclaw doctor --fix
openclaw config validate --verbose
Fix any flagged keys manually, then run doctor again.
openclaw skills sync
openclaw skills list --all
Verify all your skills appear.
openclaw browser status
If broken: openclaw browser setup
openclaw restart
openclaw status
# Skip 3.22 entirely โ install 3.23 directly
npm install -g openclaw@2026.3.23
openclaw doctor --fix
Worth it once you're past the migration. The ClawHub integration alone makes skill management dramatically easier going forward.
The 3.22 migration catches most people on corrupt configs, custom skill conflicts, or browser automation rebuilds. A second set of eyes usually finds it in under 30 minutes.
Book a $49 Recovery Session โ Or see all ClawReady services