OpenClaw 3.13 Update: Chrome DevTools MCP, Batched Actions, Fixes
Prefer to watch? Watch on YouTube · Subscribe for new builds · Read the transcript
In this video I break down the OpenClaw 3.13 update: what's actually worth knowing, what got fixed after the rough 3.12 release, and how to update. It's for anyone running OpenClaw agents who doesn't want to read the full release notes and just wants to know what matters for their setup.
I recorded this in March 2026. OpenClaw ships updates very often, so check the current docs and release notes before you act on anything here.
What I cover in this video
- 0:00 Why 3.12 caused problems and why I updated to 3.13
- 0:45 Chrome DevTools MCP with attachment mode, the biggest feature
- 3:47 Batched browser actions for faster automation
- 4:32 Android chat settings redesign and the iOS onboarding flow
- 5:18 Docker time zone override and the dashboard UI freeze fix
- 6:49 Gateway memory leak and Ollama reasoning leak fixes
- 7:35 Telegram media fixes, Windows gateway fixes, and exec approvals on macOS
- 9:55 My take and the two commands to update
Chrome DevTools MCP: your agent in your real browser
The big one in 3.13 is the Chrome DevTools MCP with attachment mode. Your OpenClaw agent can now connect to your actual signed-in Chrome. That's not a headless browser or a Playwright instance. It's your real Chrome with your logins, sessions, and cookies.
I know that sounds scary at first. But think about what it means: your agent can browse the web as you. It can check dashboards, pull data from tools you're logged into, and interact with web apps.
Here's my example. I run a resell business in the live selling niche on Whatnot. Every day I had to update profit and loss statements, go into the shipping pages, and pull numbers. Really repetitive work. I could have hired a VA for it, but now an OpenClaw agent grabs those three important numbers and updates the spreadsheet. It saves me about 15 minutes a day.
How it works:
- It runs through Chrome's own remote debugging protocol. You enable Chrome inspect and OpenClaw connects directly.
- No extensions and no weird workarounds. It's native Chrome integration.
- There are built-in profiles:
profile=userfor your logged-in browser, and a Chrome relay profile for the extension relay. Your agent knows which browser context to use without you configuring selectors.
Batched actions, mobile, and Docker
Batched browser actions
This one came from a contributor named Vincent. Before, if your agent needed to click three buttons and fill out some forms, it did them one at a time: click, wait, click, wait. Now actions can be batched together with selector targeting and delayed clicks. If you use OpenClaw for web scraping, filling out forms, or data entry, this makes it much faster.
Mobile redesign
Android chat settings got completely redesigned. The device and media sections are grouped, the connect and voice tabs were refreshed, and the chat composer is denser. iOS got a proper onboarding flow too. It used to drop you straight into a QR scanner, and now there's a welcome page that walks you through setup.
Docker time zone override
If you run OpenClaw in Docker on a server or VPS, you can now pin your time zone. Before this, cron jobs could fire at weird times because the container inherited whatever time zone the daemon was using. I run everything on a Mac mini so this doesn't affect me, but a lot of people in our community run Docker setups.
The fixes: why 3.13 is the cleanup release
This is where 3.13 really shines. On 3.12, people on Reddit were complaining about the dashboard not loading, the gateway refusing to connect, and Anthropic initialization errors. One person on the OpenClaw subreddit said they had to roll back to 3.11. The OpenClaw team even posted on their Substack about how to downgrade. 3.13 is the update that makes 3.12's features actually work.
- Dashboard UI freeze: when an agent ran a bunch of tools, the dashboard re-rendered every tool result and the whole UI froze. Now it only refreshes the persistent history when the agent is done.
- Gateway memory: stalled RPC connections leaked hanging promises forever, so the gateway slowly ate memory. There's now a bounded timeout.
- Ollama reasoning leak: with local models through Ollama, the model's internal reasoning tokens showed up in the actual response. Fixed.
- Telegram: media downloads failed on some network configs when Telegram fell back between proxy and direct networking. There's also an IPv4 fallback for fresh installs and hosts with broken IPv6. This one matters to me because my agents deliver results to Telegram every morning and I get a security check every evening.
- Windows gateway: install would hang on the scheduled task, stop wouldn't kill processes, status reported the wrong port, and off logged stale device signature errors. All fixed.
- Exec approvals on macOS: they now respect per agent settings, using configured policy with an allow list fallback. Before, gateway triggered commands sometimes prompted or got denied when they shouldn't have. I have 13 agents running on schedules, so random blocks would break my whole pipeline.
How to update
I updated the night before recording, and everything has been running smooth. Run this in your terminal:
npm update -g openclaw
openclaw gateway restart
It takes about 30 seconds. I know a lot of people hold off on updates because they don't want to break a working setup, and that's your call. Every update I've done has worked fine for me, and staying current means you get the new features.
If you're newer to this and want the bigger picture on what agents can do, check out my page on AI agents.
Key takeaways
- Chrome DevTools MCP lets your OpenClaw agent use your real signed-in Chrome through remote debugging, with no extensions needed.
- Batched browser actions make scraping, form filling, and data entry much faster.
- 3.13 is mainly a stability release that fixes the dashboard freeze and gateway problems from 3.12.
- Windows users and anyone running Telegram, Ollama, or Docker setups get specific fixes.
- Update with
npm update -g openclaw, thenopenclaw gateway restart.
FAQ
What is the Chrome DevTools MCP in OpenClaw 3.13?
It's an attachment mode that lets your OpenClaw agent connect to your real signed-in Chrome browser through Chrome's remote debugging protocol. The agent can use your logins and sessions to check dashboards, pull data, and interact with web apps, with no extension required.
How do I update OpenClaw to 3.13?
Run npm update -g openclaw in your terminal, then run openclaw gateway restart. It takes about 30 seconds.
Does OpenClaw 3.13 fix the 3.12 dashboard problems?
Yes. In 3.12 the dashboard re-rendered every tool result and froze while agents worked. In 3.13 it only refreshes the persistent history once the agent is done.
What did OpenClaw 3.13 fix for Windows users?
The gateway install, stop, status, and off commands were all fixed. Installs no longer hang on the scheduled task, stop actually kills processes, status reports the right port, and off no longer logs stale device signature errors.
Transcript
Read the full transcript
0:00Just last night I updated to 3.13 and y'all this one is packed. I'm talking like Chrome browser integration which was a huge upgrade as well as batch automation, mobile redesigns, and a bunch of fixes that people have been begging for. So, let me just tell you what's I literally just updated the setup last night right before going to bed and I was running the latest update prior to that 3.12 and if you watched my last video the other day um you know that 3.12 had some issues. People on Reddit were complaining about the dashboard not loading. There was this thing where the gateway would just refuse to connect, anthropic initialization errors. It was a mess. I even got a few messages on our school community saying did the latest update
0:45just break things for you? So, I'm going to break it down into what this actually matters for you because the release notes are pretty long and I'm going to just hit you with the features that really matter and kind of skip over the stuff you probably don't care about. So, the first thing and this is the big one is the Chrome DevTools MCP. It has attachment mode. So, what this actually means is your OpenClaw agent can now connect to your actual signed-in browser and I know that sounds scary but hold on. It's not a headless browser, not a Playwright instance, your real Chrome and with all your logins. And I know that sounds scary but all your sessions and all your cookies and if you're leveraging these OpenClaw tools and AI agents this can be very helpful especially if you're running a business.
1:30So, if you think about that for a second, your agent can now browse the web as you. It could check your dashboards, pull data from tools you're logged into, interact with web apps. So, for my example, I run a seven-figure resell business in the live selling niche on a platform called Whatnot. Everything that Every day I have to update the profit and loss statements, go into these shipping pages, and and the numbers. It was very redundant and I could have hired a VA to do it, but now I can have an OpenClaw agent take those three important numbers, update the spreadsheet, and it's all done for me. It saves me like 15 minutes a day, but again, I'm all about saving time. So, this all happens and is done through Chrome's own remote debugging protocol.
2:15So, you enable Chrome inspect and OpenClaw directly connects to it. So, there's no extensions, there's like no weird workarounds, just native Chrome integration. And they added these built-in profiles. So, you got profile equals user for your logged-in browser, and then you have profile equals Chrome relay for the extension relay. So, yeah, basically your agent knows which browser context to use without you configuring selectors and all that nonsense. Real quick, before we keep going, if you're watching this and you want to actually build with some of these tools, not just watch videos about them, then you're going to want to check out our community down below, Shipping School. We have a full Cloud Code course, a full OpenClaw course, and four live bootcamps every
3:02single week where we actually help you get set up from scratch. Like, actually set this thing up, not just watch a tutorial and figure it out by yourself. And we also provide one-on-one coaching, so you could book a call with me, we could share screens, and I can help you get Cloud Code or OpenClaw running on your machine. That's it, no fluff. I built this community because watching YouTube's only gets you so far. We launched it just 3 days ago, and we have over 55 members. You need people around you who are actually building, people who hold you accountable, and coaches who can help you when you get stuck. I'll put the link in the description down below. Get in now before the price goes up. The number two biggest update is batched browser actions. This is from
3:47the contributor named Vincent. So, before, if your agent needed to click three buttons and fill out some forms, it would need to do them one at a time. Click, wait, click, wait. It would take time. So, now I can batch these actions together with selector targeting and delayed clicks. Why does this even matter? It's speed, efficiency. It's much faster. So, if you're doing any kind of browser automation, and I know a lot of y'all are using Open Claw for like web scraping, form filling out, or data entry, this just makes it much fast. So, number three would be the mobile experience got a huge facelift. Android chat settings completely redesigned. They grouped the device and media sections. They refreshed the
4:32connect and voice tabs and made the chat composer much denser. So, if you're running Open Claw from your phone, I don't know too many people that are, but it actually feels like a real app now. And iOS got a proper onboarding flow as well. So, you know, like before, it would just throw you into like a QR scanner immediately. Now, there's a welcome page that walks you through the setup, which honestly should have been there from the start, but guys, they are shipping these updates every other day. I can hardly even keep up. But, that's why we're doing these videos to keep you up to date, so you could just watch the video, know what's relevant, know what's not, and apply it to your setup. The next one is the Docker time zone override. This sounds small, but if you run Open Claw in Docker, which a lot of
5:18people do on servers and VPSs, you can now pin your time zone with Open Claw. Before this, your cron jobs might fire at weird times because the container inherited whatever time zone the daemon was using. So, for me, I run everything on my Mac mini, and this doesn't really apply to me directly, but I do know a bunch of people in our community that are running Docker setups, and that one's for you. So, let's talk about the fixes because this is where 3.13 shines, the dashboard UI freeze. Oh my god, this one was really bad. In 3.12, I thought that this was fixed, but if your agent was running a bunch of tools, the dashboard would re-render every single tool result. So, you'd be watching your engine work and the whole UI would just
6:04freeze up. The storm of re-renders would just be consistent and they just fixed that. So, now it only refreshes the persistent history when the agent is done. And people on Reddit talking about this, too. There's a thread on the subreddit OpenClaw and it's about the 3.12 update where someone said, I quote, they had to roll back to 3.11 because the dashboard was completely broken. And I know a lot of people don't do these updates when they come out because they don't want to break what they currently have, but I do feel like doing these updates helps you expand upon the new features that are released. So, you know, if you're running like a six, seven-figure business, you're probably hesitant to update. You know, don't feel that way. Every update that I've done has worked flawlessly. Cron jobs fire
6:49off, everything is much better, but to each his own. It's different for everyone. So, the OpenClaw team even posted on their Substack telling people how to downgrade if they were having issues. So, the 3.13 update is a really like it's basically the cleanup update from 3.12. The one that makes 3.12's features actually work. So, the gateway fixes, there was this thing where stalled RPC connections would just leak hanging promises forever. So, basically your gateway would slowly eat memory because dead connections never got cleaned up. That's fixed. There's a bounded timeout now and the Ollama reasoning leak. So, if you were running local models through Ollama, their internal thinking would show up in the actual response. So, you'd ask a
7:35question and get the answer plus all of the model's internal reasoning tokens. Not ideal, but it's fixed. The Telegram fixes is a good one. You know, media downloads were breaking on certain network configs, you know, like if Telegram fell back between proxy and direct networking, file downloads would just fail. There's also an IPv4 fallback now for fresh installs and IPv6 broken hosts. So, this one actually matters to me because I run everything through Telegram. Like my whole Wu-Tang agent pipeline delivers the result to my Telegram every morning. And every evening I get a security check as well. So, basically if the media downloads broke, I wouldn't get my thumbnails, my clips, or any of that. And Windows got a ton of love. Gateway installs, gateway
8:22stop, gateway status, and gateway off all had issues. The installs would hang on scheduled task, stop wouldn't actually kill the processes, status would report the wrong port, and then off would log the stale device signature errors. All that's been fixed. And I'm on a Mac mini, so I don't feel a lot of these bumps in the road, but I do know a lot of y'all are running Windows. This update is huge for you. One more thing, the exact approvals now respect per agent settings on macOS. Before the gateway triggered commands would sometimes prompt when they should or they would deny when they should have been allowed. So, now it'll focus on configured policy with the allow list fallback. This matters for my cron jobs as I have 13 agents running on schedules. So, if the exact approvals
9:09were randomly blocking things, my whole pipeline would break. So, this is a real quality of life fix. So, here's my take on 3.3.13 is like it's a stability update. Where 3.12 was broken, a lot of this was fixed. You know, the new dashboard, the new features, that was a lot of changes in 3.12, but it shipped with bugs that frustrated a lot of people. 3.13 is the team saying, "Okay, we hear you. Let's make everything solid." And that's what I love about the Open Claw community is that when things break, people make enough noise about it, the people working on the project, it gets fixed. So, the biggest one out of it all, the Chrome DevTools integration, that's not a small feature. That is a real huge shift for anyone doing browser automation with AI agents.
9:55Being able to actually use your real signed-in browser instead of a headless instance, that opens up so many workflows. So, if you're running Open Claw, update right now, just run npm update minus g open claw inside your terminal, and then open claw gateway restart as your command. It takes like 30 seconds, and I did it just last night before I went to bed at 2:00 in the morning, and everything is running smooth. And if you want to see how I run these 13 agents and how they orchestrate and do many tasks for me to help buy back some of my time in making content and doing all that. So, it's basically all linked down below, our community shipping school. 57 members in just 5 days. And get in before the price goes up. We do four weekly bootcamp calls a
10:41week, as well as with a fifth one on the way. You don't want to miss it. We go over practical use cases using Open Claw, as well as learning how to use Cloud Code. There is full courses inside the community as well. So, I'll put it link down below, and we'll see you guys in the next one. Have a blessed day.
Ready to start building with AI?
Join the Shipping Skool community free. Paid members get live bootcamp calls every week and weekly-updated courses.
Join Shipping SkoolKeep reading
OpenClaw 4.25 Update: Phone Push Alerts, Browser Fixes, and Voice
OpenClaw 4.25 turns OpenClaw into an installable PWA, so your agents can send web push notifications to your iPhone or Android when they finish a job. It also fixes Playwright browser automation bugs, adds seven bundled TTS providers plus per-agent wake words and voices, and ships six security hardening fixes.
opencli-rs-skill: Give Your AI Agent 55+ Platforms With No API Keys
A new OpenClaw skill called opencli-rs-skill gives your AI agent real-time access to Twitter, YouTube, Reddit, Notion, and 50+ more platforms — all by reusing your Chrome login session. No API keys needed. 150+ developers starred it in 4 days.
OpenClaw 5.26 Update: Faster Gateway, Reaction Approvals, Security
OpenClaw 5.26 is a reliability release. It brings faster gateway replies, transcript-backed meeting summaries, steadier Telegram/iMessage/WhatsApp/Discord channels, thumbs-up reaction approvals, better realtime voice controls, and tighter security around untrusted browser and file content.
