OpenClaw 2026.3.13: Memory Fix, Chrome DevTools Attach, and a Smaller Android App

How to Upgrade

One command:

npm install -g openclaw@latest

Verify: openclaw --version should show 2026.3.13.

If you run into issues, check our troubleshooting guide. If you have never installed OpenClaw, start with our full installation walkthrough.

The Big Fix: Memory Usage Is Back to Normal

Version 3.12 introduced a memory regression that roughly doubled RAM consumption. Version 3.13 resolves this completely.

Chrome DevTools Attach Mode

Launch Chrome with remote debugging:

google-chrome --remote-debugging-port=9222

Then attach:

openclaw browser --attach --devtools-port=9222

This replaces the undocumented --connect-browser flag from earlier versions.

Mobile UI Redesign

The Android app is now 7MB (down from 18MB). The navigation structure changed, so custom CSS overrides for the old mobile layout will break.

Docker Timezone Support

docker run -e TZ=America/New_York openclaw:latest

Windows Gateway Fixes

Several Windows-specific gateway bugs were patched targeting named pipes and socket behavior.

What Broke

• Custom mobile CSS overrides will break due to DOM changes
• The old --connect-browser flag is gone
• Some Docker volumes may need a rebuild
• Node.js 16 is no longer supported

Should You Upgrade?

If you are on 3.12: Yes, upgrade now for the memory fix. If you are on 3.11 or older: Yes, but test first. If you are on a working setup: Do not wait too long; the security patches are meaningful.