AI Coding Rate Limits are RIDICULOUS Now - Here's How You Keep Scaling Anyway

0:00 This week, I've hit my Claude code rate limit way faster than I ever have before, and I'm not even doing that much more work. This is my max $200 a month plan. And the worst part is I also have

0:11 a $200 a month Pro subscription for Codeex, and I've almost exhausted that limit as well. And both of them aren't going to reset for another 3 or 4 days. And so, if you thought it was just you

0:22 hitting your rate limits faster, don't worry, it's not. We're all suffering from this. And unfortunately, we knew this was coming. It's been a trend this entire year. Our rate limits getting

0:32 worse, but it's just finally come to a point where I can't just be more efficient with my token usage. I mean, it's ridiculous that I have to wait three to four more days before I even

0:40 have a reset on my max plans. So, over the past half year, I've been doing a lot of experimentation with using different models, especially open ones, in my AI coding workflows. But now,

0:51 that's gone from just experimentation to, okay, I absolutely need this as a crucial part of everything that I'm doing. I mean, look, the proof is right here. And that's not just me. As an

1:01 industry, when we get more into harness engineering and loop engineering and software factories, whatever your AI coding workflow looks like, we're trying to scale the output with our coding

1:09 agents. But now, even more than before, the biggest limiter is just the number of tokens that we can spend. That is why we need to strategize and figure out for our larger AI coding workflows, not

1:19 single agent, where do we absolutely need the largest and most capable LLM versus other places where we can use something that is smaller, cheaper, faster, and still get basically the same

1:29 output quality. And yes, that is possible. Trust me, I've been deep in the lab this week expanding on all the research I've been doing this year figuring out for a traditional AI coding

1:39 workflow where you have your planning, implementing, validating, and reviewing, where do we need the best LLM versus where do we not? That's the big question to answer right now so you don't hit

1:49 your rate limit 3 days into your weekly reset. So, for all the testing that I've done this week, I've done it with my AI software factory. I've covered this system a lot on my channel recently. It

1:59 takes all my best practices for AI coding with planning and implementing and validating. It packages it up into a complete system where I can send in scope of work and it just builds and

2:09 validates everything without me in the loop at all. It's the ultimate test of how autonomous can we make AI coding while still keeping it reliable. But more importantly for this video, it

2:19 allows me to very easily test different combinations of large language models with the full development cycle. So, what I've been doing is building a bunch of different applications with the AI

2:29 software factory, including this video game that I'll show you today. It just makes for a nice and visual core example, but all the other things that I built, the results I got is pretty much

2:38 the same as what I got with the different combinations for this game. So, building the same game, but with only open models, using claude, and using codecs. A lot of other testing

2:47 that I did as well, but these are the three core columns. And so essentially I just took the best model from each group, right? With open models, DeepSeek V4.1 Flash is pretty much the best of

2:59 the best. So if we look at like the live LLM benchmarks here as far as open models go with that open tag, Deepseek V4.1 Flash is the best right now. And then for Claude, Claude Fable 5.1 max

3:10 effort is the best. And then for Codeex, GPT6 Astra max effort is the best. And so going back here for my core testing with open models, I'm using Deepseek Flash for planning and reviewing and

3:21 then GLM 5.3 Flash for the implementation. And I actually did this as a baseline where I used it for implementation for every single test and then for Claude using Fable for planning

3:31 and reviewing and then for Codeex using Astra. The most important thing here is you'll notice I'm always using the more capable LLM for planning and reviewing and then the smaller model for building.

3:41 This is something that I've determined in my experimentation this week and a lot of what I was doing earlier this year as well. The most important step of your AI coding workflow is always the

3:51 plan step. If you have a well-written plan, the implementer following that, it doesn't even have to be that capable of an LLM to pretty much get the best results possible, right? Like using

4:01 Fable for planning and implementation gets you essentially the same results as using Fable for planning and sonnet for implementation. So that you'll see that very intentionally laid out in all the

4:12 testing I show you today. And by the way, for implementation, generally that's the most tokenheavy part of your workflow. So for using the smaller model for that, that is what prevents us from

4:21 hitting our rate limits super quickly. Now, obviously for some work, if it's very very difficult and unexplored, you might want to use a large model for everything. And I don't do this in my

4:31 software factory, but if you do have human in the loop, really small and bounded tasks, you can use an open model for literally everything. So there's different combinations that make sense

4:40 in different situations, but this is generally what I recommend. And I'll show you a lot of my testing that has led to this, but for me, my favorite flow right now, my favorite combination

4:50 is to use GPT6 Astra for the planning and the review and then GLM 5.3 Flash for the super fast and cheap implementation. This is my core workflow for everything that I'm doing right now

5:02 with my software factory. And even outside of that, the sponsor of today's video is Scribba and they just released something incredible called Explain. You ask a question and it gives back a fully

5:13 narrated video lesson in 2 to 3 seconds built live while you watch and it plugs right into Codeex and Claude Code. So now over in Cloud Code, I do SLMCP. We can see I have Scribba explain

5:25 connected. It was just a single command to do this. And so now I can ask Claude Code to make an explainer for anything. And so I thought this would be a neat demo here to show it making a Scribba

5:34 explainer for a more complicated pull request from my open source project Archon. So here Claude reads the diff, it builds up the lesson and then it streams to Scribba slide by slide. So I

5:44 get the link right away. I can watch it as it builds the explainer. And I got to say the explainer that I got back here at the end, it genuinely impressed me. Let me show you. So this is the original

5:53 poll request that I made the explainer for. And then here is the video. So I'll just shut up for a second and play a couple of the clips here. PR 3416 gives three adapters one shared way.

6:04 >> I'll go to a more high level diagram here is the contract that the CLI adapter and the web adapter implement the it goes into the code as well. Click a little bit further here

6:14 >> lives in core. The helper accepts any object which lets the headless platform pass its structurally identical work. >> Cool. So I'm not going to play the entire thing obviously but yeah it

6:23 sounds great and it's breaking things down really nice and simple for me. I love it. Explain also works from chat GBT and as a Chrome extension for any article. Give Explain a try for free

6:33 with my link in the description. Now, the question you might have at this point is how exactly do we build a larger AI coding workflow where we're using different models and providers?

6:43 Cuz maybe you want to implement the same way I am. You want to experiment like I am. Whatever it is, there are a lot of different ways you can do this. The most manual but simple way is just to have

6:52 each coding agent output a handoff document as markdown. So you feed that into the next model or the next coding agent. And so you just go through one at a time opening up different coding agent

7:03 sessions. There are also harnesses out there like Omnien that make it very easy to work with models and different providers in this way. But what I do for my AI software factory and my coding

7:14 workflows in general is I simply use my open- source harness builder archon. This makes it really easy for us to build these workflows that I've been running hundreds of times the last week

7:24 to combine different models and providers. So for every single test that I ran, every single combination of models, the shape always looks like this as an archon workflow. And I'll show you

7:35 what the workflows look like in a little bit. So the input is always a GitHub issue that describes what we want to build. Then I have the most powerful model do the planning like GPT6 Astra as

7:44 my favorite. We take that plan and then within the archon workflow we automatically pass that into the next node which is GLM 5.3 flash doing the implementation and then we have Astra

7:55 review and then any findings it sends back to GLM to correct and we have that loop with obviously max retries and then we have the check at the end which is just running our tests making sure the

8:04 build is green before we do the merge at the end of the software factory. And so this is a pretty traditional AI coding workflow. There's nothing crazy here. This is the exact shape for every single

8:16 test I ran. There are also a lot of different ways to access open models for our AI coding workflows. But my favorite recently, especially because Archon supports this, is to use PI as the AI

8:27 coding agent harness and then for accessing the LLM using Neon's AI gateway. I've always loved Neon. I love their Postgress database solution. They've been adding a lot of other

8:36 really cool AI features as well like AI gateway and all their other new back-end features like object storage, authentication, and functions. But yeah, for right now I'm using AI gateway,

8:45 which gives us really reliable and at cost access to pretty much every open model that you could hope for. So, for example, we have Kimmy K3. Uh, what else do we have here? We got GLM 5.3 Flash,

8:55 which I've been talking about a lot. And so, this is just my easy way to access all the models that I need within my Archon workflows and with PI. But regardless of how I am accessing these

9:04 open models, the important thing is that I am I'm not just using Astra or Fable for everything like a lot of us are tempted to do. And you can do this setup with anything. You don't even need

9:13 Archon. It's my tool. It's free and open source and I use it to run the AI software factory. But also, I'm not telling you you have to go use my tool at all. Right? Like this is just what

9:22 I've been doing for my experimentation to give these results to you and help you think about what models to use, what combination. And so for my Archon workflows, this is a bit of a simplified

9:31 view, but pretty much every single one of them looks like this, right? We have the planning step at first where we're using the more powerful model and then we take that plan markdown document as a

9:42 handoff to go into the build step with the cheaper model like GLM 5.3 flash through neon and then review with more powerful again and then fix anything that came up with the cheaper model.

9:52 This is the shape even beyond my experimentation here for just generally how I work with coding agents now. Okay. So I wanted to spend good time explaining my workflow, my

10:00 experimentation and the models that I recommend. But now I want to get into the actual game with you as the core example here just to give you a visualization of the results that I've

10:08 been getting across all the different apps I've been building. This again like I said at the start of the video is very much the results I got no matter what I was building. And so the first version

10:16 of the game looks terrible. You can probably guess this is what I built with only open models. And so by the way this game is an idea from a friend. It's really cool. So I thought I'd put this

10:25 through the factory. It's a weather chasing like stormchasing game on Neptune. It's actually multiplayer. We can have different people join and man the stations here. I won't set that up

10:35 right now, but it's pretty comprehensive game that it gave us that PRD into the software factory. And so this version of the game, I used open models, so Deepseek V4.1 Flash for the planning and

10:46 reviewing. And then for the building, I use GLM 5.3 Flash. Now, the visuals are so bad, you can't even really tell that I'm moving. There's a couple of the clouds we can see outside the windows.

10:56 But yeah, we can see the heading changing in the top left as I'm turning around as the pilot. But overall, this isn't even really a good starting point for a game. And then for the next

11:04 version of the game, this one was built entirely with Claude because I wanted to show you an example here where we aren't using open models at all. I used Claude Fable 5.1 to build this entire thing.

11:16 And yes, for the sake of tokens, I couldn't do something super comprehensive. So, I unfortunately wasn't able to make something that looks like super beautiful, but I mean, this

11:24 still looks pretty good. Definitely a lot better than just the open models. And let me uh go over to the pilot here. I wish I could run, but I'll go over to the pilot and show you that things look

11:33 a lot better. Like, if I take the controls here and I uh change the heading, you'll see that like I It's a little bit choppy, but I'm moving towards the clouds. And then when I go

11:42 forward, the clouds are actually getting closer. Like, the navigation on the planet is actually working pretty well here. It'd be cool to show you all the other stations as well, but would take a

11:51 lot of time. The point is that Cloud Fable 5.1, it did a pretty good job for the very initial proof of concept for this game. I didn't allow that many tokens, but yeah, it's pretty good. The

12:01 next version of the game, I am genuinely impressed. Not that it's like actually amazing, but the fact is I used GLM 5.3 Flash to write every single line of code in this version of the game. And then

12:14 for the planning and reviewing, I used GPT6 Astra. And so this version of the game was about four times less tokens or like less cost overall because I'm using GLM for the implementation and it plays

12:30 pretty much the same. Actually, the moving is even smoother here going towards the clouds. I would say this version of the game actually is better even though I was using an open model to

12:40 write every single line of code. So, of course, it helps to have Astro Review, but I'm still saving a ton on my cost/ rate limit by using this combination of models. And so, yeah, a little bit of a

12:51 cheesy game, very much just a proof of concept. But the point here is this is the results that I got for pretty much every application that I built. And remember, going back to the live bench

13:01 here, Claude Fable 5.1 and GPT6 Astro, they're pretty close in capability. And so it's pretty awesome that we were able to build even a little bit of a better game and other apps with this

13:11 combination compared to just using claw. That is the proof you need. You don't always have to have the best large language model for every step of your process. It is well worth your time and

13:23 I hope I've really proved it here to analyze your AI coding workflow. figure out where you need the best model and where you don't because that is what's going to prevent you from jacking up

13:32 your rate limits for your subscriptions like Claude and a codeex. And so my AI software factory is how I've been doing all my testing, how I run my workflows now, but whatever you're currently doing

13:44 this this lesson applies like you should really explore open models at this point because it's becoming clear that we can't always run on our frontier models. So, I hope that you found this testing

13:54 interesting as I'm going through all these different combinations, building out different apps. If you did, I would really appreciate a like and a subscribe. Follow along as I continue to

14:02 build out my software factory and test these combinations. And with that, I will see you in the next