Subscribe to OpenClaw News
One short email when we publish. No spam, unsubscribe anytime.
OpenClaw 5.12 Fixes
OpenClaw 5.12 ships stability fixes
OpenClaw, the open-source AI agent framework built by Peter Steinberger and now stewarded by an independent foundation, released version 5.12 this week. The update strips the install down to a core, isolates Telegram, and adds recovery for stalled model responses, all answering a wave of community complaints about broken setups and wiped memory.
The release lands at an awkward moment. As of May 10, 2026, Hermes Agent, built by Nous Research, overtook OpenClaw to hold the #1 position on OpenRouter's global daily app and agent rankings, generating 224 billion daily tokens versus OpenClaw's 186 billion. OpenClaw still leads cumulatively, but the daily flip is the first time it has been displaced since its late-2025 rise.
Why this release matters
OpenClaw is a personal AI agent that runs locally and connects to messaging apps like Telegram, WhatsApp, Slack, and Discord. Think of it as a digital assistant that lives inside the chat apps you already use, rather than in a browser tab. OpenClaw's founder, Peter Steinberger, joined OpenAI in February 2026, and the project moved to an independent open-source foundation with OpenAI as a sponsor. Since then, the maintainer team has been under pressure to prove the project can ship clean releases without him at the helm day-to-day.
That pressure is visible in the framing around 5.12. The release notes lean on words like "faster" and "harder to wedge" rather than touting new features. The creator of the source video, reviewing the changelog, argued that the team is finally focused on the right things: stability over surface area.
What actually changed
The headline change is that OpenClaw is no longer a kitchen-sink install. Previously, installing the core pulled in libraries for every supported channel: WhatsApp, Slack, Amazon Bedrock, Anthropic Vertex, and the rest, whether you used them or not. That meant slow installs, bloated memory, and more surface area for things to break.
In 5.12, those integrations are now installed on demand. Connect Slack and the Slack libraries come down. Connect Bedrock and Bedrock libraries arrive. If you run OpenClaw on a Raspberry Pi or an older machine, this should translate into a faster startup and fewer mystery crashes from code paths you never touch.
Telegram, which has been a sore spot for months, got dedicated attention. The gateway, the central process that routes messages, tools, and memory, used to handle Telegram polling alongside everything else. If it got busy, Telegram messages would simply pile up unseen. 5.12 moves Telegram polling into its own worker, writes incoming messages to a local backup file, and improves stall detection so outbound traffic no longer masks a stuck inbound queue. A separate fix stops the agent from trying to download images from group messages it was never meant to respond to.
Stalled streams and a smarter command line
The most useful fix for anyone running agents in production is stalled stream recovery. When a language model stops sending tokens partway through a response, perhaps because of a dropped connection or a hung upstream server, the agent used to sit there indefinitely. 5.12 detects the stall, rotates to a backup model or login, and surfaces an actual error if recovery fails instead of going silent. A community member named Tashin called this the fix that matters most for production setups, because an agent that hangs is one you cannot trust.
Other meaningful changes in the release:
OpenAI setup default: new installs now default to the ChatGPT subscription path (Codex) rather than asking which method you want. The API key route is still selectable.
Web chat scroll: auto-scroll is now configurable. You can follow new output, stay pinned to the bottom, or turn it off entirely and use a "new messages" button.
Better error messages: when a channel fails to connect or a setting is broken, the command line now prints the exact command to fix it.
Security: Windows home folders are blocked from the agent sandbox by default, credential handling moved to a structured system rather than raw environment variables, and the phone-to-gateway pairing flow is stricter.
Plugin installs: pnpm 11 support, better dependency handling, and a code safety scanner that no longer false-positives on deep transitive dependencies.
Is 5.12 enough?
The lighter install, the Telegram isolation, and the stalled stream recovery are the right kind of work. They are unglamorous, they will not show up in a demo video, and they directly address the things that have been driving users away. OpenClaw still has the broadest channel coverage of any open-source agent and one of the largest contributor bases in the space.
But one release does not rebuild trust. The next three or four updates will decide whether 5.12 was the start of a turn or another false dawn. If the next update breaks Telegram again, the daily ranking gap will widen.
What This Means for You
If you run OpenClaw and your current setup works, do not rush to update. Wait a few days. Watch the project's Discord and the release thread on X for reports from people who tested it first. The cost of a broken Slack channel is higher than the benefit of a slightly faster install.
Before any update, run the built-in backup command, every time, no exceptions. Write down the version number you are currently on so you have a clean rollback target. If you do update and something breaks, check the Discord before you start debugging from scratch. Someone else has almost certainly hit the same bug and found a fix.
If you are choosing an agent framework today and have not committed to one, the realistic call is to pick based on what you actually need. OpenClaw still wins on raw integration breadth. Hermes is shipping faster and has the daily usage lead. Whichever you pick, learn it deeply. The people who get value out of AI agents over the next year are the ones who master one tool and build real workflows, not the ones who jump frameworks every time something breaks.
Further reading
Source: www.youtube.com
Helpful documentation
Get notified when we publish new articles
No spam, unsubscribe anytime.
By subscribing, you agree to our Privacy Policy.