ClawHosters
by Daniel Samer
3 min read
Dashboard v2 shipped on March 13 with v2026.3.12. By that evening, power users were filing bug reports. Sessions with tool-heavy agent runs locked the browser completely. Chrome's "page unresponsive" dialog showed up after 30 seconds of frozen rendering. The v2026.3.13 release landed the next day with the fix.
If you're on ClawHosters, this is already live. You got the regression and the fix without touching anything.
The Dashboard Freeze and What Caused It
Here's what was happening. Every live tool result during an active agent session triggered a full chat.history reload. The frontend fetched the entire conversation and re-rendered it synchronously on the main thread. Run a web research agent with 40+ messages, and each incoming tool result stacked another 200-400ms of blocking. After a few rounds, the tab was dead.
Issue #45194, filed March 13, documented users seeing a blank chat pane with an oversized OpenClaw logo despite the backend responding normally. Earlier reports in Issue #44107 had already flagged that sessions with 80+ messages (roughly 156KB) caused Chrome to give up entirely. PR #45541 by @BunsDev fixed the core problem: live tool results no longer trigger full history reloads. Only the final completion event refreshes persisted history.
The gateway never crashed during any of this. Agents kept running fine. It was purely a frontend rendering issue, which means no session data was lost.
Mobile Gets a Serious Cleanup
Android ships a redesigned chat settings sheet with grouped sections, a denser composer layout, and a refreshed Connect tab. The app is down to roughly 7MB. iOS now shows a welcome pager before gateway setup instead of dropping new users straight into QR pairing. The auto-QR scanner is gone. Instead, you get step-by-step /pair qr instructions. Windows gets a timeout on schtasks calls with a Startup-folder fallback if task creation hangs.
As Nerdschalk noted, this release is about practical usability rather than headline features. If you missed the previous release coverage, that one focused on the built-in safety scanner.
OPENCLAW_TZ Pins Docker Container Timezones
New environment variable. Set OPENCLAW_TZ=Europe/Berlin (or any IANA timezone) in your compose file, and the container stops inheriting UTC from the Docker daemon. Cron jobs fire when you expect them to.
Issue #3318 requested this in February and was closed as "not planned." Then v2026.3.13 shipped it anyway. Docker-only feature. Native installs already inherit the host timezone and don't need it.
If you're running scheduled agent tasks on ClawHosters, your timezone is handled in your instance configuration. For background on our security hardening approach, that's covered separately.
