OpenClaw v2026.3.31
Stability, Security & Infrastructure
Addressing User Pain Points in the Agentic Ecosystem
Unified Task Control Plane
- The Problem: Orphaned background tasks from ACP, cron, and subagents.
- The Fix: SQLite-backed task ledger.
- Visibility: New CLI surface:
openclaw flows list|show|cancel.
- Detached work now bubbles back to the parent session correctly.
Security Overhaul
- Plugin Safety: Installs now "fail closed" on critical findings. Override required.
- Semantic Approval: Narrow read tools auto-approve; exec tools ALWAYS require user confirmation.
- Gateway Hardening: Explicit tokens now required for local-direct fallback.
New Channels & Features
- QQ Bot: Bundled channel with multi-account & media support.
- Matrix: Added streaming (in-place updates) and room history.
- WhatsApp: Agents can now use emoji reactions ❤️.
- Teams: Member info resolution via MS Graph.
Pain Points Addressed
| Pain Point | 2026.3.31 Fix |
|---|
| Orphaned tasks | SQLite Unified Task Ledger |
| Plugin supply chain risk | Fail-closed installs |
| Stalled LLM streams | Configurable idle-stream timeout |
| Tool over-approval | Semantic approval classes |
| MCP collisions | serverName__toolName spacing |
OpenClaw vs. Hermes Agent
- OpenClaw: Best for Teams, 20+ channels, complex routing, and the vast ClawHub ecosystem.
- Hermes Agent: Best for Solo Operators, zero-telemetry, and self-improving skills from daily tasks.
- Benchmark: Hermes leads in personal productivity (7-3); OpenClaw wins on infrastructure breadth.
Practical Verdict
Use OpenClaw for multi-channel deployments and team governance.
Use Hermes Agent for personal automation and an agent that learns from you.
Many power users run both on the same VPS.