Published: 2026-05-15
Deep dive

OpenClaw 5.12: Lighter Installs, Telegram Fixes, and Stability Wins

Chapters / key moments (click to jump — plays here on the page)

OpenClaw 5.12 arrives as a direct response to months of buggy updates that eroded user trust and allowed Hermes Agent to surpass OpenClaw in OpenRouter API call volume for the first time. The release focuses on three structural improvements: channel libraries now install on demand (not bundled at setup), Telegram message handling runs in an isolated worker process that can't be starved by other activity, and a new stalled-stream recovery system auto-rotates to a backup model when the AI stops responding mid-conversation.

Source video

"OpenClaw 5.12 Update: What You Need To Know…" by Julian Goldie SEO — Watch on YouTube →

Key Takeaways

Install footprint cut dramatically—WhatsApp, Slack, Bedrock, and Vertex libs only install when you actually configure those channels.
Telegram moved to an isolated worker: missed messages during busy gateway periods are now saved to a local backup file and stall detection no longer counts outgoing messages as "healthy."
Stalled-stream recovery detects when an AI model stops sending data and rotates to a backup model or login instead of hanging silently.
Windows home folders are now blocked from the agent sandbox—passwords, SSH keys, and credentials stored in your user profile can't be accessed accidentally.
Recommended approach: wait a few days before updating, run openclaw backup first, note your current working version number as a rollback target.

Behavior & security changes worth knowing

Modular installs. Channel libraries (WhatsApp, Slack, Bedrock, Vertex) no longer install with the core — each one installs only when you actually configure that channel. Faster install/startup, less memory, fewer crashes from libraries you weren't using. Especially noticeable on a Raspberry Pi, small VPS, or older machine.
Windows home folders blocked from the agent sandbox (security). Your agent can no longer accidentally read passwords, SSH keys, or other sensitive files in your Windows user profile. Provided credentials now flow through a structured system instead of reading arbitrary environment variables, and phone/browser pairing got stricter.
OpenAI default changed to the ChatGPT-subscription (Codex) login. When you set up OpenAI now, it defaults to the ChatGPT subscription route instead of asking. If you use a separate API key, you can still choose it — but the default now matches what most users actually have.
Telegram isolation + stall recovery. Telegram runs in a dedicated worker so it can't be starved during busy periods; missed messages are saved to a local backup file. When a model stops streaming, OpenClaw now rotates to a backup model/login and shows a real error instead of hanging silently.
Plugin tooling: pnpm 11 support, better add-on dependency handling, and the add-on safety scanner no longer blocks legitimate add-ons over deep-dependency code.
Web-chat scroll controls: choose follow-output, always-follow, or auto-scroll-off with a "new messages" button — fixes the auto-scroll-yank that made long replies hard to read.

How to update safely (the video's advice)

This release landed during a rough stretch of buggy updates, so the creator's update procedure is worth following for any production setup:

If your current setup works, don't rush. Wait a few days and watch community reports before updating.
Back up first, every time:
```
openclaw backup
```
Write down your current working version as a rollback target.
Test on a separate user profile or server if you can, confirm it works, then move your main setup.
After updating, run openclaw doctor to catch config drift.