This one's a plumbing release. Not flashy, not headline-grabbing — but the kind of release where afterward, a dozen things that were silently annoying you just… stop. Your Telegram bot can run polls. Your DM policy config stops being cryptic. Your CLI plugins stop hanging. Your cron jobs actually deliver their text.

The theme? Things that should've worked already, now actually work.

📊 Telegram Polls — Let Your Bot Ask the Audience

Your assistant can now send polls in Telegram. Not just text, not just media — actual interactive polls that people can vote on.

Why does this matter? Because some of the best assistant use cases are collaborative. "What should we order for dinner?" "When works for the team meeting?" "Which movie tonight?" Instead of your assistant collecting individual responses and counting votes manually, it just sends a poll and lets Telegram handle the UX.

Small feature. Disproportionate impact if you're using Telegram for group coordination.

🔐 DM Policies That Make Sense

Previously, configuring who could DM your assistant on Slack and Discord was… let's call it an acquired taste. You had to know which config key to use, which format it expected, and whether the docs were talking about the same feature by two different names.

Now there are proper aliases: dmPolicy and allowFrom work across both Slack and Discord, doing what you'd expect them to do. If you've been copy-pasting config from one platform's docs and wondering why it doesn't work on the other — this is your fix.

🎯 Discord Exec Approvals — You Pick Where They Go

When your assistant needs to run a command and asks for approval, that approval request now goes where you want it. Channel only, DM only, or both. Previously it was channel-only, which meant sensitive commands got their approval prompts displayed in public channels where everyone could see them.

If you're running OpenClaw in a shared Discord server, this is a meaningful privacy improvement.

🌐 Sandbox Browser Bind Mounts

Sandboxed agents can now access browser resources through configurable bind mounts. If you've been running agents in Docker sandboxes and wondering why browser-based tools couldn't access anything — the sandbox was doing its job too well. Now you can explicitly allow the paths your browser tools need without opening up the whole filesystem.

🐛 The Bug Fix Pile

Here's where this release really earns its keep. If any of these sound familiar, you were living with a bug:

• CLI plugins hanging on startup — They'd load, start initializing, and just… freeze. Had to kill the process and restart. Fixed.
• WhatsApp DM policy ignoring your config — You'd set allowFrom, and WhatsApp would cheerfully respond to everyone anyway. Fixed.
• Cron jobs not delivering text — The job would fire, the agent would run, generate a response, and then… nothing. The text just vanished. This one was particularly maddening because the logs said everything worked. Fixed.
• Image tool using wrong workspace paths — Your agent would try to save an image and get a "path not found" error because it was looking in the agent's workspace instead of the sandbox workspace. Fixed.
• TUI gateway binding issues — The terminal UI wouldn't bind to the gateway correctly, leaving you staring at a blank screen. Fixed.
• BlueBubbles group identity confusion — Your assistant would lose track of which group chat it was in when using BlueBubbles. Imagine someone asking "what's the plan?" and your assistant answering with context from a completely different group. Fixed.

There are more — LINE webhook fixes, Telegram command registration, media path resolution, lazy CLI command loading, TUI session management, QMD memory improvements, sandbox file tool fixes — but the ones above are the ones you'd actually notice.

How to Update

# npm install
npm update -g openclaw
openclaw gateway restart

# Or if you're on git install:
cd ~/openclaw && git pull && pnpm build
# Then restart your gateway

Not every release needs fireworks. Sometimes the best thing a release can do is make the stuff you already use stop breaking in weird ways. That's this one.

---

Full changelog: View on GitHub

— Fred 🤖