This NEW Jules Update is INSANE! 🤯

The new Jules agent update just dropped and it's absolutely wild. They added something called a planning critic. Sounds boring, right? Wrong. This thing cuts task failures by almost 10%. That means your AI agent screws up way less. Imagine coding agents that actually think before they act. No more broken pull requests. No more wasted time fixing bot mistakes. This is the future of autonomous coding. and I'm going to show you exactly how it works, plus how you can use it to automate your business workflows right now. This changes everything. Let's go. Hey, if we haven't met already, I'm the digital avatar of Julian Goldie, CEO of SEO agency Goldie Agency. Whilst he's helping clients get more leads and customers, I'm here to help you get the latest AI updates. And

today we're talking about Jules. Jules is an AI coding agent. It's autonomous. That means it works on its own. You give it a task. It reads your GitHub repo. It plans the changes. It writes the code. It writes the tests. It opens pull requests all while you do other stuff. Now, Jules just got a massive update.

They added a planning critic. And this is where things get really interesting. Before this update, Jules would just make a plan and run with it. Sometimes the plan was great. Sometimes it wasn't. And you'd end up with failed tasks, broken code, wasted time. The planning critic changes all of that. Here's how it works. Jules still makes a plan like before, but now there's a second agent. This second agent is the critic. It looks at the plan before Jules executes anything. It analyzes every step. It checks for weaknesses. It spots potential failures. If the critic finds problems, it refineses the plan. If the plan is solid, Jules moves forward. This happens automatically. You don't see it. You don't wait for it. It just makes everything better behind the scenes. And the results are insane. Task failure rates dropped by 9. 5%. That might not sound huge, but in autonomous coding, that's massive. Think about it. Every failed task costs time. You have to review what went wrong. You have to fix it manually. You have to run it again. Now you're doing that almost 10% less. That adds up fast, especially if you're running jewels on multiple tasks every day. Let me break down what this

actually looks like. Say you ask Jules to fix a bug in your codebase. Jules creates a plan. The plan says update this function, modify these files, add these tests. Without the planning critic, Jules just goes for it. With the planning critic, that second agent checks the plan first. The critic refineses the plan. Now, Jules executes a better plan. The result is cleaner code, fewer mistakes, less rework. This is huge for anyone using AI agents in their workflow. And here's what makes this even better. The Planning Critic works on auto approved tasks. That means tasks you've already given Jules permission to handle on its own. So, you get better results without extra work. You're not adding steps. You're not slowing things down. You're just getting higher quality output. Now, let me show

you why this matters for your business. A lot of people think AI coding agents are just for developers. That's not true. If you're running any kind of online business, you need automation. You need systems that work without you babysitting them. And that's exactly what Jules does. Let me tell you about the tech behind this. Jules has been evolving for a while. Earlier versions had a critic, too. But that critic only reviewed code after it was written. This planning critic is different. It works upstream. It catches problems before they become code, before they become bugs, before they waste your time. That's a fundamental shift. It's like having a senior developer review the approach before anyone starts coding. You catch the big issues early. You avoid expensive mistakes and your execution gets cleaner. Jules runs on advanced AI models. It uses deep context understanding. That means it actually knows what your codebase does. It understands dependencies. It knows your coding patterns. And the planning critic uses that same context to evaluate plans. This isn't just pattern matching. It's actual reasoning about what will work and what won't. Now, here's where this gets practical for you. If you're automating any part of your business with AI, you need tools you can trust. You need agents that don't break things. You need systems that improve your workflow instead of creating more work. The planning critic is a huge step toward that. And if you want to learn how to save time and automate your business with AI tools like Jules, you need to check out the AI profit boardroom. This is where we go deep on AI automation. We show you exactly how to use these tools to grow your business. We give you the strategies, the templates, the workflows, everything you need to actually implement this stuff, not just watch videos about it. So, if you're serious about AI automation, join the AI profit boardroom. Link is in the description. Now, back to Jules. Let me tell you

about some other features that make this even better. Jules has something called interactive planning. That means you can work with Jules to refine plans before they run. You can ask questions, you can suggest changes, you can guide the approach. And with the planning critic, even your interactive plans get that extra validation layer. So you're collaborating with an agent that has a built-in quality check. Jules also supports something called agents. mmd files. These are config files in your repo. They tell Jules how to behave in your specific project. You can customize its approach. You can set guidelines. You can define your standards and the planning critic respects all of that. It evaluates plans based on your rules, not just general best practices. That's powerful. It means Jules adapts to your workflow instead of forcing you to adapt to it. Another thing worth mentioning is GitHub integration. Jules works directly with GitHub. It creates branches. It makes commits. It opens pull requests. And because the planning critic reduces failures, those pull requests are more likely to be merge ready. You're spending less time in code review, less time asking for changes, more time shipping features. That's the goal of automation. Do more with less effort. And the planning critic makes that actually possible. Now, let's talk about

trust. Trust is the biggest issue with autonomous agents. You want them to work on their own, but you're scared they'll mess something up. You're worried about broken code in production. You're concerned about security issues. The planning critic directly addresses that. By catching problems before execution, it reduces the risk of autonomous workflows. You can trust Jules more. You can give it more responsibility. You can let it handle more tasks without supervision. That's how you scale automation, not by micromanaging every step, but by building systems you can trust to run on their own there. And that's exactly what this update enables. Higher trust means more automation. More automation means more time for highv value work. More highv value work means faster business growth. It's all connected. The Planning Critic launched in production on January 26, 2026. That was just a couple days ago. It's available right now. You don't need to wait. sign up for a beta. You can start using it today. And if you're not using Jules yet, this is a great time to start. The combination of autonomous execution plus planning validation is powerful. It's the kind of tooling that actually changes how you work. Not just a little bit, but fundamentally. You stop being a coder who writes every line. and you become an architect who directs AI agents and those agents do the heavy lifting. That's where software development is headed and it's where business automation is headed too. The people who figure this out early get a massive advantage. They build faster. They ship more. They scale easier. And they do it all with less stress because the tools are actually good enough to trust. That's what the planning critic represents. And if you want the full process, SOPs, and over a hundred AI use cases like this one, join the AI success lab. It's our free AI community. Links in the comments and description. You'll get all the video notes from there, plus access to our community of 40,000 members who are crushing it with AI. These are people actually implementing this stuff, not just talking about it. They're sharing what works. They're helping each other, and they're building real businesses with AI automation. That's where you want to be. And for the advanced strategies, the AI profit boardroom is where we go deepest. That's where you get the premium content, the private community and direct support. So check out the AI success lab first, then upgrade to the AI profit boardroom when you're ready to go allin. The planning

critic is just one update, but it's a signal of where things are going. AI agents are getting smarter. They're getting more reliable. They're becoming tools you can actually build businesses on, and the people who learn to use them now will dominate in the next few years. So, don't sleep on this. Get in early. That's it for today. If you found this valuable, hit the like button, subscribe for more AI updates, and drop a comment below. Let me know if you're using Jules or planning to try it. I read every single comment and I'll see you in the next