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

How to avoid unexpected OpenRouter costs in OpenClaw automation
A developer team accidentally spent $750 in 3 days on OpenRouter by defaulting to Claude Sonnet 4.6 ($3/M tokens) across all automation tasks. They reduced costs by 97% by changing default models, locking cron jobs and subagents to cheaper options, and reserving expensive models only for sensitive work.

The LLM Voice Problem: Avoiding AI-Generated Writing Patterns
A developer discusses the common issue of LLM-assisted writing having recognizable "LLM-isms" that trigger immediate AI detection, and shares an article on identifying these patterns and editing for authenticity.

Research Shows Effective AI Prompting Is Cooperative Communication, Not Engineering
Peer-reviewed research indicates that effective prompting with AI models follows the same cooperative communication principles humans use, with Lakera's analysis showing most prompt failures stem from ambiguity rather than model limitations.

Running OpenClaw Locally with Ollama to Avoid API Costs
A Reddit user shares their experience switching from API-based OpenClaw to running it locally with Ollama, eliminating API costs while maintaining workflows. They created a step-by-step installation video guide.