OpenClaw 4.10 Update: What's New (Release Notes Breakdown)

0:00You're not going to believe it. Another OpenClaw update. We are on 4.10 now when we just upgraded to 4.9 a few days ago, but 4.10 has a massive feature that is going to be really helpful if you're struggling with memory. And I'm going to break it all down in this video as two reasons why you should consider upgrading your OpenClaw. So, 4.10, what does it exactly add? And why does it even matter? And where does this fit if you're already running a setup like me? Because the worst thing to do is when you have a working OpenClaw setup, and then you update because you think that feature is going to be amazing, and then your whole setup breaks and you spend days getting it back to where it was actually functional. But, that's why I make these videos to keep you up to date

0:45to see if it's even worth for you to upgrade. This is not one of those updates where I just read a change log and pretend every line changes your life. It's a real improvement in a few spots that affect daily use in this latest The big thing with 4.10 is really simple. OpenClaw is getting much better at memory, cleaner with model routing, better on Mac for voice dictation, and tighter on security. That's the update. Take care. Just kidding. We're going to dive deeper. Those are the four pieces I'm going to cover mainly. The active memory is the most intriguing. The Codex provider split, local MLX speech, and the security hardening work. I want to go through it in the order that matters

1:30most. Because memory is a big issue, and we need to tackle that first. Then, I will tell you why you should care. Then, I will tell you how to use them effectively. Then, I will compare this to the setup I'm already running with 17 agents, memory files, neon database, super memory for cloud memory, and lossless claw. Because that's really the question. No, it's not new. Is it useful is the real question. First, let's talk about what's actually in 410. The first feature is active memory. They've made massive improvements to the memory just these last few updates. This moves memory from something passive into something that actually gets checked before the assistant responds to you. Instead of hoping the right context is sitting in the current chat, the system

2:15can now search memory first, pull what matters, and use that in the reply. Real quick, before we keep going, if you're watching this and you want to actually build with some of these tools, that just watch videos about them, then you're going to want to check out our community down below, Shipping School. We have a full Claude code course, a full Open Claude course, and four live boot camps every single 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 Claude code or Open Claude 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

3:01just 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 second feature here is also the Codex provider split. Codex-style models now get their own provider path instead of being mixed in to the same route as normal Open AI chat usage. That means cleaner auth, cleaner thread handling, and less weird crossover between coding workflows and regular chat workflows. The third feature is local MLX speech on Apple silicon Macs. So, if you're using talk mode on the Mac, more of that

3:46speech flow can happen on the device. Faster, more private, and less back and forth on the cloud. And the fourth piece is security hardening, better browser navigation defenses, better checks before exec actions, better plug-in install scanning, more guardrails around the risky parts, too. That's the feature list. Now, I'm going to talk about why each one of these matters in the real world. I'm not just here to tell you about the features and go peace out, bye. I want to tell you how you can actually use them if you're running on an older version of OpenFlow. The thing here that intrigued me the most is always going to be memory. They updated it with active mem. This matters because repeating yourself sucks. If you've used Open AI or if you used AI for more than

4:31a week, you've have felt this. I have to. You tell it how you like things written. You tell it your priorities. You tell it what project matters. Then 2 hours later, you're explaining the same stuff again like you just met. I hate that. That breaks everything. That breaks the flow, that breaks your focus, and it's quite annoying. The flow is everything when you're trying to get work done. Have you ever heard of the flow state? I mean, this literally breaks your flow from building. Basically, if the assistant can search memory before it answers, you get less of that goldfish brain behavior. Less reminding it that you hate fluff, less reminding it that your business has priorities, less reminding it what already happened yesterday. It's not just about convenience, either. It's about better decisions, more context the system can recover at the right moment,

5:17the less likely it is to give you a generic advice or response that ignores your actual situation. Now, the Codex provider split is an interesting one here. This matters because routing matters more than people think. Your mix model families through messy paths, you get strange behavior. One tool acts one way, another thread behaves differently, auth gets pretty confusing, compaction gets inconsistent, and then when something goes wrong, you're stuck wondering if it was the prompt, the model, the provider, or the thread state. It's just a nightmare. A dedicated Codex route means coding work can behave like coding work, and regular OpenAI chat can behave like regular chat. Cleaner separation, easier debugging, less time chasing ghosts. And

6:04if you're running multiple agents on different models, this matters a ton. Once you've got a main brain writing agents, coding agents, and cron jobs all doing different stuff, clean routing stops being a nice extra and starts being real infrastructure. Another one, too, is local MLX speech. This matters because voice only feels good when it's fast and private. If voice is laggy, people stop using it. If voice feels creepy, people stop using it. Running speech on device fixes a lot of that. Your Mac already has serious power if you're on silicon. So, using local speech means lower delay, less dependence on outside services, and less concern about where your audio is going.

6:49I personally use Whisper Flow. I love it. But, sometimes it doesn't work and it's very annoying. So, I'm happy to see this get upgraded in Openclaw. A lot of builders want to talk to their assistant. If you're not doing that, what are you doing? 2026, get with the program. I like to brain dump ideas. I like to get an idea, go to my Openclaw, and hold a button down, and just brain dump everything in an unorganized way. That way, my agent gets the big picture. It's a great way to capture ideas, run quick commands, but they want it to feel natural. If every voice interaction has drag, you won't stick with it. So, this feature matters because it removes that drag. Then, you've got security hardening. And this matters because agents are powerful enough now to mess

7:34things up in a hurry if you're sloppy. If an agent can browse, install plugins, and run commands, you need boundaries. Real ones, not just good vibes, man. Better browser protections matter because the web is messy. Redirects happen, bad pages exist. Better exec checks matter because a model can be overconfident. It can think it's editing the right file and still be wrong. Better plugin scanning matters because third-party code is always where the thing gets kind of dicey. So, when I look at this part of the update, I don't see boring maintenance. I see the team taking Blast Radius seriously, right? Let's talk about how to use each feature. Because if you install an update and never change its behavior, nothing changes. With active memory, the first thing you want to do is think about what deserves to be remembered.

8:21Preferences, obviously, right? Repeating workflows, important context, ongoing projects, decisions you've already made. Then make sure your memory system is storing useful stuff instead of random junk. The point is not to save everything. The point is to recover the right thing when needed. Once active memory is turned on, pay attention to whether replies start feeling more aware without you re-explaining yourself. If it misses something, inspect it. Look at what it pulled and what it didn't. Memory gets better when you treat it like a system, not magic. Now, for the Codex provider split, usage is mostly about setup clarity. If you're using Codex for coding work, put it in the lane made for that. Keep your regular OpenAI chat models in their own lane. Then test the real workflow. Open a coding task, watch how threads behave,

9:07watch whether compaction feels cleaner, watch whether the off feels less janky. The point is to notice if your day gets smoother. For the local MLX speech, if you're on Apple silicon Mac, this is the one of those features where you should just turn it on and try it out in a real session. It's not a demo, it's a real feature. Use it to capture thoughts, ask for quick help, run talk mode in a way you'd actually run it during the day, then compare it to the cloud voice in your head. Did it respond faster? Did it feel more natural? Did you feel better knowing the audio stayed local? That's the true test. And with the security changes, the main thing is to respect what they are there for. Don't treat guardrails like an annoyance. Treat them like brakes on your fast car. You want them there before you need them. If you're using browser actions, be

9:52intentional about what you allow. Like if you're using exact, slow down and read what the system is about to touch. If you're installing plugins, keep your standards high. More capability is good if you can trust it. Here's the part where I think is the most, I guess, interesting about these updates. Like how does this compare to the way I already have my system set up? Just talking to a lot of people in the group today and I tell them, "Don't update unless you really need to. My system's working. So do I need to update? I got memory on lockdown." Here's why you should update. You know, I'm not coming at this like some random beginner. You know, I'm not like a super expert, but I have been running OpenClaw for over 2 months now. And I run my whole content pipeline through this thing. And it works. If you're struggling to keep up with content, well I'm about to save you

10:37about 40 days worth of work. [music] I built something called Content Machine. It's 10 AI agents that run on the OpenClaw orchestration and they handle everything. Scripts, thumbnails, X posts, [music] blogs, outreach, clips, newsletters, all of it. So I went from 1,000 subscribers to 4,000 subscribers on YouTube in 7 days using this exact system. Every single morning I wake up and the content's already done. I spend maybe 15-20 minutes reviewing and approving them and I move on with my day. [music] It works for any niche, fitness, finance, real estate, marketing, whatever you are building and it is 100% completely customizable to your use case. [music] So you get the

11:22mission control dashboard, all of the cron jobs, everything I've built over the last 40 days helping me gain more and more people to subscribe and join the community. So you plug in your own thing and it molds it to you. It learns how you talk and it writes so it doesn't sound like AI slop. $97 one time. It's not a subscription. [music] I'll put the link down below and you'll thank me later. I've got 17 agents running. I've already got memory files figured out. I've got Neon as the database where we push unstructured data. I've got super memory as agent containers for when the heartbeat cuts off, it stores the memory. I've already got lossless claw handling the conversation continuity during compaction events. So, where does 410 fit in your life? If I'm already

12:07doing this and maybe you're doing this, why should we update? Here's my straight-up take. Active memory does not replace a serious memory architect. It improves the default behavior inside of Open Claw itself and that's the important difference. In my setup, memory is already a full system. Like I have daily memory file. I have long-term memory. I have database records. I have searchable history outside memory services. So, for me, active memory is not some magical first memory layer. It's another retrieval layer inside of a product that helps the assistant use context more consistently. Like it is still has value because even if you've built a bigger memory machine around Open Claw, it still helps when the chat itself can recover context before replying. Same with the code X split. Like if you're already running a stack with different model roles, this is less

12:52about unlocking a new idea and more about making the plumbing cleaner. My main chat and my specialist agents are already have different jobs. So, cleaner provider separation fits how I think anyway. One tool for one type of work, another for another type of work. Less crossover, less confusion. As far as the local MLX speech, you know, I love that. Like if you've already got a strong Mac based system like Whisper Flow, local speech just makes the machine more self-contained and I like that. That's a win. I like anything that keeps useful compatibility close to the device instead of sending everything out to someone else's server. And on the security side, if you're running 17 agents, this part matters even more because the more moving parts you have, the more chances there are for careless action to create a mess. One bad browser

13:38action, one bad plugin, one wrong exact call, that's all it takes. The stronger safety checks are not just for beginners, they're for power users, too. So, when I compare Open Claw 4.10 to the system I already run, I don't see it replacing the custom stack. I just see it making the base layer a lot smarter. And that's really good because the better the base layer gets, the less duct tape you need around it. You still want memory discipline, you still want a database, you still want outside retrieval if you're serious. You still want clear agent roles. You still want continuity systems like lossless claw. None of that goes away, but 4.10 pushes the default product right in the direction we all want to see. Better memory behavior, cleaner model routing, faster, more private voice on a Mac, tighter safety, risk, and security

14:24actions. That's real progress here. If you're brand new, this update makes Open Claw easier to trust. If you're already deep into it like I am, this update makes the foundation even better under the setup you've already built. This release does not change the mission. It makes the machine better at supporting the mission. And when you're trying to build a business with agents, that's what you care about most, reliability, not hype, better daily operation. That's what 4.10 gives you. If you want to build AI agents like this and maybe you're struggling and you're sitting on the sidelines watching all these cool people make cool things with AI. That's what our community is about. I have 219 people that joined and I just launched this community 25 days ago. We have people building in Korea, in Russia, in the Netherlands. And I live in Oregon, but we have people all around the world

15:09joining these calls and we do nine live calls every single week where we meet you where you're at. We help you take the next step wherever you're at. You're getting Claw code installed, maybe you haven't even gotten Open Claw installed, but you have a Mac mini sitting in the corner, we want to help you take the next step. We want to help you build an AI agent workflow. And that's what we do in the community. Like I said, nine calls a week. We have other teachers in there as well. We do have courses in there, but we're focused on human-to-human interaction. I'll put the link to it down below. You could check it out. And if you haven't subscribed to the channel already, we release about two, four to six videos every single day. Hit the subscribe button. We cover AI news and all things Open Claw. Have a blessed night. Bye-bye.