Three things from the OpenClaw community worth actually reading this week — a performance milestone, a rare transparency post, and a competitive data point that changes how you think about the ecosystem.
1. v2026.5.12 Drops: 3.5× Faster, Leaner, Harder to Break
OpenClaw's v2026.5.12 release (mid-May) is turning heads for doing exactly what overextended power users have been asking for: trimming the fat. WhatsApp, Slack, Amazon Bedrock, and Anthropic Vertex dependencies are now externalized — the core runtime only pulls what you actually install, resulting in a leaner initial footprint and faster startup. But the bigger headline is performance: the team measured a 3.5× improvement in end-to-end round-trip time, validated by automated Telegram bot-to-bot tests running every six hours on Blacksmith CI — real production-like channels, not synthetic benchmarks. Telegram itself gets its own isolated polling worker with local message spooling, stall detection, and preserved HTML/Markdown formatting in streamed replies, so the flakiest channel in most production setups finally becomes boring reliable. Luke The Dev (@iamlukethedev) called it a "big" release and summed it up simply: "lighter, safer, and much more dependable."
https://x.com/iamlukethedev/status/2055030630866379207
2. The OpenClaw Security Manifesto: What's Actually Getting Fixed
After the 13 CVEs and the ClawSwarm campaign rattled community trust earlier this spring, the OpenClaw team published "Where OpenClaw Security Is Heading" on May 15 — a rare transparency post that names the specific tools being built rather than making vague promises. The lineup: fs-safe, a shared library of root-bounded filesystem patterns that blocks path traversal and symlink escapes across core, plugins, and services; Proxyline, a Node-level network egress router that enforces policy (blocking metadata services, private ranges, loopback) at connection time rather than at URL validation; ClawHub trust evidence, a full pipeline combining ClawScan, VirusTotal, static analysis, and moderation to tag every plugin release as clean, suspicious, quarantined, or malicious; and OpenGrep, running 148 rules derived directly from past GitHub Security Advisories on every CI diff and PR. Perhaps most practically, Tree-sitter parsing is now used to detect destructive commands buried inside bash -c wrappers before the approval prompt fires — targeting the "prompt fatigue" that pushes users into YOLO mode. The post doesn't claim zero-risk. It claims observable, bounded risk — which is exactly what production deployments need to hear.
https://openclaw.ai/blog/where-openclaw-security-is-heading
3. Hermes Agent Just Topped OpenRouter's Daily Rankings — and OpenClaw Is Still Standing
For the first time, Nous Research's Hermes Agent surpassed OpenClaw in daily token throughput on OpenRouter's public leaderboard, peaking at 271 billion tokens processed in a single day (May 9) versus OpenClaw's 245 billion. MarktechPost covered the shift in detail, noting Hermes has been climbing fast on the back of its self-improving "do, learn, improve" skills loop, persistent memory, and a community swelling with OpenClaw migrants since its February 2026 launch. OpenClaw isn't toppled — it still holds the cumulative crown at approximately 9.1 trillion total tokens versus Hermes's 6.3 trillion — but the daily metric is the real-time pulse of momentum, and it's now pointing at Hermes. Community reaction on r/singularity ranged from "healthy competition makes both better" to "I saw this coming in February," with no sign of OpenClaw loyalists switching camps in panic. Two agent runtimes competing in public, measured by real throughput data: this is what a maturing ecosystem looks like.
Spotted something great on X about OpenClaw? Share it — the community is the best part.