OpenClaw 3.22 Upgrade Checklist: Practical Steps from a Developer Who Got Burned

Before Updating to OpenClaw 3.22
Check your .env file for any CLAWDBOT_ or MOLTBOT_ prefixed variables. Version 3.22 removed all of these variables with no fallback or compatibility. If you have them, your agent won't start and the error message won't be helpful. Rename everything to OPENCLAW_ first. If you set up OpenClaw before mid-February, you almost certainly have at least one of these variables.
Run openclaw backup create before touching anything. Consider tagging your current Docker image as :pre-upgrade so you can roll back instantly if needed.
After Updating to OpenClaw 3.22
Run openclaw doctor --fix which catches most config migrations automatically.
Check /tools in any channel to see what tools are actually available. Version 3.22 changed the plugin SDK surface (moved from openclaw/extension-api to openclaw/plugin-sdk/*) so third-party plugins using old import paths will just silently not load.
Run openclaw secrets audit to find plaintext API keys in your workspace. The developer found two that were completely forgotten, sitting in skill config files.
New Features in 3.22
/btwside conversations- Native ClawHub install from CLI (
openclaw skills installinstead of manually downloadingskill.mdfiles) - Dead session cleanup
- Cron retry backoff so a failing job doesn't drain your API budget overnight
- 48-hour agent timeout instead of 10 minutes, which means long tasks actually complete now
The developer recommends budgeting 30-45 minutes for a careful upgrade instead of assuming it will be smooth, noting that after it's done, "it's genuinely better."
📖 Read the full source: r/openclaw
👀 See Also
Your Agent Is Not the Model: Harness vs Inference Service Explained
A quick reference distinguishing model, inference service, and harness in AI agent systems. Use Claude CLI or Cursor? This breakdown helps debug issues and design better agents.

Contract Testing for AI-Driven Development with OpenClaw
Contract testing can replace integration/E2E tests when using AI agents like OpenClaw, focusing on interfaces and invariants between components. The AI generates code to satisfy deterministic contracts, creating a tight feedback loop for faster iteration.

CLAUDE.md Files Are Often Organized for Developers, Not AI Models – Here's Why That Matters
CLAUDE.md files commonly place Hard Rules at line 47, after background and tech stack. By the time the model reads constraints, it has already constructed conflicting assumptions. A better structure puts hard rules first.

Practical Guide to Creating Claude Skills: Structure, Triggers, and Scripts
Claude Skills are instruction manuals that automate repetitive tasks, stored as folders with a SKILL.md file in ~/.claude/skills/. The guide explains YAML triggers, script integration, and multi-skill orchestration rules.