OpenClaw Update 3.31: But is it Enough?

Summary

OpenClaw 3.31 is a stability and security-focused release rather than a flashy feature update. You'll find significant security improvements including fail-closed plugin installs that block malicious code by default, addressing the fact that roughly 10% of ClawHub plugins were previously flagged as dangerous. Gateway authentication has been tightened so local processes can no longer access your gateway without proper tokens. The biggest architectural change is the unified background task control plane, which consolidates all background jobs from ACP subagents, cron jobs, and CLI into a single SQLite-backed system. This means you can finally track, view, and cancel tasks using three new CLI commands instead of dealing with ghost processes. If you've been using Claude with adaptive thinking, the broken /by-the-way command is now fixed. MCP support has improved with authentication headers, proper tool name collision handling through namespacing, and configurable per-server timeouts. Platform updates include QQ bot as a first-class channel, Matrix streaming support, and WhatsApp emoji reactions. The video addresses whether OpenClaw is still worth using compared to Windsurf and Claude Code Computer Use. OpenClaw wins if you're running multi-channel deployments with teams and rely on the ClawHub ecosystem. Windsurf wins for solo operators who want faster onboarding (under 15 minutes) and an agent that learns from daily work without telemetry. In benchmarks, Windsurf beat OpenClaw 7 to 3 for personal productivity in core agent comparisons, though the gap narrows to roughly 6 to 5.5 when considering OpenClaw's full ecosystem. The presenter ranks Claude Code Computer Use first, Windsurf second, and OpenClaw third personally, though acknowledges OpenClaw remains viable if your current setup works well.