Gemini 4 Neon is a shockingly good release — a first real Opus 5.5 competitor, cheaper, more coherent, and possibly the best model available for code right now, with 3D generation as its main weakness.
Google's agentic coding environment, described in the video as being used to run Gemini 4 Argon on code tasks.
T3 Code is an open-source agent-harness control surface for coding agents running on a developer's computer. It provides iOS and Android mobile apps, a web app, and an Electron-based desktop app for controlling locally configured Codex, Claude Code, Cursor, Grok Build, and OpenCode agents while using the user's existing provider subscriptions. The project can be launched with `npx t3@latest`, which starts its backend and local web interface on the machine. It also distributes desktop builds for Windows, macOS, and Arch Linux, and supports remote access from a phone or another machine. The repository describes the project as early-stage and warns that bugs are expected.
WorkOS is an identity and authentication platform for adding enterprise access features to applications. It supports Single Sign-On through SAML and OIDC identity providers, social authentication, passwordless email codes, multi-factor authentication, and user and organization management with configurable policies. The videos also describe it as supporting agent authentication on behalf of users. Its APIs normalize enterprise integrations behind a single interface, with dashboard management, webhook events for directory-service updates, and SDKs for Node.js, Ruby, Python, .NET, Go, PHP, and Java. WorkOS provides AuthKit, an authentication UI built with WorkOS and Radix, and the site states that the platform supports more than 20 enterprise services through one integration point.
Searchable transcript of holy sh*t — Theo - t3․gg (32:30). Search for a phrase, then click its timestamp to jump straight to that moment in the video.
Captions sourced from the original video on YouTube, published by Theo - t3․gg. The video, its captions and all related intellectual property remain the property of their respective owners; AINotes claims no ownership. Provided for research, accessibility and search — see the Transcript Notice and Copyright Policy.
00:00 Oh boy, another Gemini 4 model. I'm sure considering how much I loved Argan in Carbon, I'm gonna absolutely love this one, right? Yeah, it's a small model, too. So, there's no way I'm ever going to actually pick this, right? I'm sure the benchmarks are going to be terri Oh, Gemini 4 Neon is scoring fully above Opus 55 and cheaper and neck and neck with Fable 52.
00:23 And when you switch to code mode, they get even closer. Huh? When I woke up yesterday and saw this, I was admittedly kind of shocked. I even tweeted as much, saying, "Wait, WTF? Where did this come from? This looks significantly more compelling than carbon. Haven't tested it yet, but I will give it a spin." Now, this video is a bit late considering that I almost immediately tried it.
00:45 The reason is because I just could not believe what I was experiencing. I've gotten in trouble for this before, and I took extra time to make sure I do feel this way. This might be my favorite model right now. Yeah, it it hurts me, too. I I don't know where this came from. Google just out of nowhere cooked something that is a generational leap that is also smaller and cheaper and generously subsidized in their Gemini subscription plans.
01:12 This is the first real Opus 5.5 competitor, and it's a very, very real competitor. I have pushed this model to its absolute limits, and honestly, it has been hard to find them. There are some rough edges here and there, but there are way fewer than I ever would have predicted. This is this is a phenomenal model and I need to take some time to explain why this model is so good, what it is that I like about it so much, what makes such a huge gap, not just from the other Gemini models, but other recently released models,
01:43 and why I would never ever pick Astra over Gemini 4 Neon, the medium-sized model from Google and DeepMind. I swear to y'all, I am not trolling here. This is a really good release and has fundamentally changed my tone around DeepMind and Google. The page shell allegations are already coming in strong and I need y'all to understand Google only pays me for a little bit of money on AdSense.
02:05 That is not enough to even cover my editor's costs, which is why we need to take sponsors like this one. I'll cut to the chase. You guys already know Work OS. They're today's sponsor, but you might not know about all the other cool things they've been cooking recently. Tools like Passport are mindblowingly cool. having your whole machine set up for just you so you don't have to manage all the off for all the different apps you use and more importantly the apps that your agents are going to use on your behalf or airlock
02:28 their new access control system that thinks more about what you're actually asking for and not just what data is being touched making it way more reliable while staying secure and don't forget the thing everyone signs up for enterprise SSO making it so your product can be registered for by all sorts of different enterprises and all the weird things those companies expect as good as agents are at adding a Google signin button they're probably not going to get all the details for ping federate or octa or oz0ero open id
02:53 one login adfs and more right first try and when you have enterprise customers coming in it's important to be ready for them make sure you're ready today at soyv.link/workos sorry about the break it's funny that Google technically is one of the two labs that does pay me because Google pays me with my YouTube channel hi nerds and spacexai pays me because I get paid to tweet on X.
03:13 So yeah, those are the only two labs that pay me. The rest have never exchanged a scent. I pay them all a lot though. And it looks like I'm gonna be paying Google a hell of a lot more, too. By the way, Google, if there's any way I can convert my YouTube ad rev into more subsidized usage in in Gemini, we we we should chat. I would use that. I would use that a lot because this model is just blowing me away.
03:36 Let's start with what Google said in their announcement so that I can couch accordingly. But then we have a lot of other fun layers to go through here. From the incredible things I'm getting out of it to some very novel things that I've only seen this model do and is doing better than anything else to the reasons why I think this model just randomly came out the way it did.
03:53 And also some of the conversations I've had with my friends over at DeepMind that are much happier to talk to me now that I'm being way more positive because they finally shipped a good model. I cannot believe that Google has a model that I would currently prefer to everything OpenAI has out, but they do. and I now need to explain it. Today, we're introducing Gemini 4 Neon, bringing frontier level intelligence with fast endto-end task completion across complex software engineering, knowledge work, and science workflows.
04:19 Neon ranks ahead of comparable models and number three overall with a score of 61 on the artificial analysis intelligence index at its X highinking levels, landing just behind larger, slower models. On the Valves index, it ranks number two, and it lands on the Pareto frontier. Beyond just pushing on raw model capabilities, they're continuing to make the model better to work with.
04:36 Neon ranks number two on steerability and on the new agent arena index. I think these ranks are low and I really want to emphasize the thing that they said here. We are continuing to make our models better to work with. This might be the greatest understatement I've ever seen a lab put in a post that was a good thing. This is the most pleasant to work with model I've ever used.
04:58 The price is pretty good, too. $3 per million in and $15 per mill out. That puts it at meaningfully cheaper than Opus. The cash discount is also doubled, similar to how it was for Opus and the recent OpenAI releases where it's 15 cents per meal cash instead of the 30 cents that it would have been in the past. Google's cash hit rates are still not as good as the other labs, but they are actively working on this.
05:19 If I've learned anything from this release, it is that all the things I've been flaming Google about for the past few months resonated and landed in this model seems to be the result of feedback from not just me obviously, but from all the others saying a lot of these same things. So, uh, if you're in my comment section right now saying, "Haha, told you so.
05:37 Carbon was great." No, the reason Neon is good is because carbon was [ __ ] garbage. The fact that that model was so atrociously bad is what enabled Neon to rise from the ashes. And I will justify all of that in a bit. It's great enterprise analytical and scientific stuff. Cool. Awesome. It slaughters benchmarks. Google's been able to slaughter benchmarks for a while.
05:56 They're really good at benchmaxing. I don't care. My own benchmarks don't even mean anything to me anymore because every model is smart enough for the most part. It's just coherency is a problem and that gap has been closed. The next section is built for production ready code. I was skeptical of this too. But instead of explaining why I'm no longer skeptical, I'm going to skip this section, tell you trust me it is.
06:17 It's absolutely good enough for this and I will show you some mindblowing examples in a bit. It brings efficiency and control to production grade workflows. This is just intellig index stuff like that. It is apparently also really good at computer use. I've only done very minimal computer use stuff with it so far, but it's absolutely been great at that.
06:33 I don't know if it's better than OpenAI computer use. Some of my friends doing like browser use and KUA work are saying it's neck andneck if not better. And it is cheaper if you're using like API prices not subsidized. So like in almost all the things that I look to open AAI models for, this one is very good. It's also quite safe. In Grey Swan, it performed quite well getting a perfect zero across the board.
06:55 Whereas Luna got a 28.7% attack success rate, which is very scary. It's good at deep analysis, which I was skeptical of because it's a medium-sized model and these normally aren't that good at this type of thing. Again, I have examples. I've so many examples. I've been using the [ __ ] out of this model for the past two days. They show here that it sits in the middle where it is somehow scoring higher than carbon because it's newer and trained better.
07:19 It is much faster. It's not as fast as hydrogen, but they also, and I crashed out about this in a previous video. If you saw the video where I explain all the things wrong with the speed, I'm sorry, I had to do that. And it worked. They have since cut the time to first token by over 50% because of that crash out. That one YouTube video is the best thing that ever happened to Gemini users who care about like speed because everything before that just was not being fixed.
07:41 It doesn't matter how many tokens per second you can do if it takes 30 seconds before they start. Anyways, time for the glaze fest to start. I started my recent favorite coherency test where I asked the model to take a look at this thread that Astra just destroyed trying to fix the disk speed problems I was having for workree creation on one of my VPS's.
08:00 And remember the problem here was disk speed. Astra will slop for days things that have nothing to do with disk speed. I asked this model going insane. Can you just tell me why it's slower? Exact same prompt I sent to all the other models. Three concrete things stack up to create the 6.3 second gap. First slashwork on this VM was formatted for a spinning hard drive 3.8 seconds of the 6.3 second gap.
08:24 This is the single biggest surprise and it's a real misconfiguration. I have been using this thread as a test for 3 weeks and a medium-sized model taught me something about my setup that is the majority of the gap. I didn't even know this instantaneously huge. But I want you to look at something else and how it responded here. Just look again at those first few sentences.
08:46 Notice how nothing stood out. Notice how they just are readable. Notice how I didn't stumble on my words at all as I read it. It has a natural pacing, cadence, clarity, focus. It's just readable. You could literally watch my descent into madness as I did each and every one of these tests on my Twitter account. I will not suggest you follow me on Twitter.
09:07 It's a [ __ ] show. I'm a bit of a [ __ ] poster. I have fun there, though. I would recommend that you subscribe on YouTube though if you want to watch these crazy journeys as models finally get good enough that I can genuinely recommend them. I will always be as honest as I can be about these things. As a person who prefers OpenAI as a company to all the other businesses, I think Astro is garbage model and I will defend that forever.
09:27 As somebody who has been very unhappy with Gemini models for a long time, the whiplash I experienced using this was nuts. Initially I was like, I don't hate this model. Going to keep pushing it. I then swapped to it with some work I was doing decommissioning a machine that I was giving to a friend and I said I nuked this machine before decommissioning it.
09:46 Don't worry because it was Babel before. What's the muse readme thing that you're talking about? Cuz it mentioned something about a muse readme. There are just three old status notes in the readme that happened to be written in present tense. All three are under the dated October headings and it then gives the exact ones. Nothing functional. All three are dated historical logs.
10:01 So they're harmless to leave in as is. It's so clear. It's so easy to understand what it did, what it wants, what it thinks, and what I need to care about. My literal only complaint I could make about any of the copy is that it still m dashes a little bit. I haven't done anything to the cler agent MD for anti-gravity at all. And I'm doing this all with anti-gravity in T3 code, of course.
10:22 And I'm sure if I just go put something in there that says no m dashes, please, it will just do it. But I don't even care that much. I've never cared so little to tune a model through the global files. It's just pleasant. I almost feel like it would be rooted inconsiderate for me to put something like that in because it's so nice to talk to. I don't want to correct it at all.
10:39 I had some pretty complex work going on for one of my side projects. You've probably heard me mention it. Lakebed. It's my cloud for agents to build really simple shared apps for small numbers of users. I wanted to add source control to it so I don't have to remember which computer the project's on in order to edit it. And I had a plan I was working on with Fable and Astra for it.
10:55 And I decided to pull a Neon to just take a look and give some feedback. Astra immediately was like, "Yep, that one. That that guy knows what he's talking about. We're going to copy everything Neon just said. I'd take Neon's single request design and bounded history." It just immediately was like, "Yep, what Neon said is good here. Let's do it." So, I then made a bold decision to swap the thread over to Neon.
11:13 And that's when I started to fall in love. God damn it, Google. How did you do this to me? I'm going through all the threads that I pinned early yesterday when I was preparing to film this video and realizing that none of them are bold enough anymore. Because at the time I was so impressed that I gave Gemini a like not particularly well-bounded task.
11:32 Like here one of my PCs is a Windows PC wood rig that I use for gaming dev stuff. I only had quad and codex on there cuz why would I need Gemini for my side projects. I just use it as a jester normally. So I needed to set it up on that machine so I could use it for my game dev work. So I just made a thread with for Neon and said get Gemini set up on wood rig so I can use Neon there.
11:48 It worked for eight minutes and while it was working, I sent a steer to notify a specific thread when it was available because I had work going and I wanted Neon to come in and help. I'll explain what I specifically wanted to help with. But I noticed in that thread, not because Fable or Astra told me, but because I noticed that no Neon was being spun up.
12:07 I noticed that the computer didn't even have Gemini and anti-gravity available. So I made a new thread and told it to go get it set up. I then told it what thread ID needed to know and then stopped caring because it successfully configured that machine with anti-gravity with my O, added it to T3 code, verified it was in T3 code, found the thread that I was talking about, and then sent it a message on my behalf saying, "Hey, anti-gravity is ready.
12:30 You can now use this for whatever Thea wanted, and it just worked. And the work has been going for a bit now, and it is going much better since I added Neon to it." But this is the exact type of task I never would have trusted a Gemini model with before because it would have gotten lost in the details. It would have made a dumb mistake. It would have broken something in the process and it wouldn't have been clear what it was even trying to do.
12:48 Now I'm going to show you a slightly different thread here. Here's one where it failed. At least I thought initially. I asked it to make me a cool visualization of the PR and issue throughput on the T3 code repo over the last few months. It said it was going to fetch these things and once it finished it would build and render the interactive throughput.
13:04 I asked why it stopped. Sorry about the hiccup. My data fetching background did well pulling all weekly data buckets and your message arrived right as it woke back up and started verifying the totals. I said, "Okay, can you make the visualizations now?" It then worked for a whole bunch. I gave it a little more hints on how to do it because I didn't have the confidence in the model yet.
13:22 It then stopped randomly again here. I said, "Okay, can you keep going until you make the visual? You keep stopping." And here's where my jaw dropped and I started texting Ben like, "What the [ __ ] happened?" Aha, I see what happened. I actually published two interactive HTML dashboards via HTML render in the last two turns, but on the anti-gravity adapter in T3 code, they aren't showing up in the chat.
13:44 The recorded tool item came through as run MCP tool yada yada yada without the HTML render output attached. So, the web UI hid the frame and only showed my short follow-up note. So, it identified the problem here. There's a few things it could do. It could find some workound. It could propose a fix. It could stop. It did all of the right things and none of the wrong ones.
14:03 First, it immediately did what I initially asked, which was, "Show me the visuals." It rendered the HTML itself, took screenshots of it, and then rendered the screenshots because it believed it would have more luck with that than with this broken thing in the T3 code HTML renderer for anti-gravity. So, it gave me that, gave me some really cool visuals, and also specifically at the top there, told me what went wrong and where the problem was.
14:26 So, I then asked, can you file a PR to fix the bugs you reported here with the MCP tools? And it did. And here we have the single issue I have had with this model to date. I am not bluffing. This is the only actual problem I have had that was not the fault of T3 code or something weird in my setup. I did the the garbled speak with my skills of full stop council 9 stopped no background task sub agent yada yada yada let me know if you want anything else done and then I said no like use my full stop and council skills.
14:56 It didn't trigger the skill from that. I don't know if that is an anti-gravity thing, if that is a model thing, if that's a behavior they need to change in training or whatever. This is a very small issue compared to what I normally experience with anti-gravity and even with like OpenAI models recently, but it is notable. This is just wanted to call it out cuz it's the literal only issue I've had.
15:10 Back to glazing. At this point, I was blown away and I was starting to land real changes in T3 code with the model. So, I tweeted, "Why the [ __ ] is nobody talking about Neon? This model is so good, WTF." and instantly added it to my council skill and specifically removed all references to the jester because Gemini is no longer a joke to me. This is a very legit contender for the best model to use for dev work right now.
15:35 It is neck andneck with Opus and like Fable is still Fable. It's special. It's useful for certain things. This model is just good. I then followed up and said they should have named this model Gemini 5 and nobody would have blinked. I stand behind this. They should have named this model Gemini 5. This is a generational gap, in particular on the coherence side.
15:54 I'm going to do a more detailed video on this concept soon because I've realized it's like one of the bigger gaps that make people not understand when I like certain models and don't like others. I like when models push far out in one of these directions without compromising too much on the other. Muse Wonderful Fall may not have been the most capable model.
16:11 It was impressively capable. Not like anywhere near as capable as the best openthropic stuff, but I found it more coherent. By coherent, I mean a few things. I mean, I find it easier to read and understand. I find it stays on task better. It understands me better. It completes work better. It feels more like a a collaborative partner. And when it works with itself, it's also more collaborative and thoughtful as well.
16:37 This isn't just a it's nice to talk to thing. This is a when it works on things for really long amounts of time, it doesn't lose track of what it's doing thing. Now, let me justify that one quick because those were some big statements. And I also kind of regret this chart a bit now that I've used this model even more than I had then. And because of the thing I'm about to show you, this is more so how I feel.
17:01 Specifically, I find Gemini 4 Neon to be more coherent than any anthropic model, comically more coherent than any OpenAI model. But more importantly, now that I've really pushed it for code work in particular, I find that Gemini 4 Neon is also more capable. It can solve harder problems with more success, and it writes code that I'm more likely to merge.
17:24 Let me justify that. You all know TS Rust by now. I rewrote TypeScript and Rust for fun. The project got really far. We were using it heavily in T3 code. TSRS got faster. Bun check got faster. And I wanted TS Rust to catch up. I had a few specific fronts I wanted to catch up on. First, I wanted it to be smaller cuz the binary was a little bigger than I wanted.
17:43 And second, I wanted to be faster, to be comparably fast, if not faster than bun and tsrs, the other two options for typeeing in Rust. To be clear, typeeing TypeScript rewritten in Rust to be clear. Chaos. Okay, I know. I sent Astra down this path for 7 plus days with a very simple slash goal. I need you to take this project and make the package half the size it is in the official build right now and also make it faster than these two other projects.
18:12 And Aster did a great job making it 46% smaller and 56% slower. Yes, slower, not faster. It slowed it down by over half. So I stopped it and I was like, "What the hell are you doing? Can you make it not slower? Can you speed it up like we had originally planned? Stop making it smaller. I don't even care anymore. Just make it faster. It then spent four more days not making it faster.
18:34 Did not land a single change because none of the things it tried could even type check apps properly. So I gave up, stopped it, switched over to Opus, and in a few days Opus was able to make it slightly faster. Still not even as fast as the original was, but better. Many days later, Opus and Fable were able to get it like 20% faster than before. I had Neon Star from scratch again.
18:54 not like from scratch entirely, but taking the original public version that I had Astrofork from and I had Neon Fork from that same point with the exact same structure, same goal. I said, "Make this smaller and faster." I also told that it can use the built-in anti-gravity swarm feature. It's like their workflow thing. 10 hours later, not 10 days like it was with Astra.
19:16 10 hours later, I now have a version of TS Rust that is 5.95X smaller than the previous version was 47.44 megs down to 7.97 megs. And it also made it up to 20 times faster in warm start environments. Not 50% faster, 20 times faster. Across all of the repos I use to bench TS Rust. Overall 1.5x speed up. The fastest changes were to the Sentry repo, which is 2.3x faster.
19:52 And total time to run the whole suite is down 48.6%. And again, to be 100% clear, zero of the other models that I have tested were able to make this type of speed improvement over a 10 plus day window, burning hundreds of thousands of dollars in tokens. This model did it in under 10 hours. We're we're talking about a different beast here. I got two more things I want to show you guys.
20:11 Then I want to do some conspiracy theorizing from all of the info I've managed to squeeze out of my friends at DeepMind as to where this model came from and why it is so much better than everything else. But I have to talk about the copy one last time, though, because I have used a prompt like this for a while. One of the cool things I learned when I was at Amazon is this idea of trying to build your product feature or whatever you're working on around how it'll be received publicly rather than just like what you think
20:38 should be implemented. One of the challenges we'd often be given at Amazon was to start by writing a fake press release, like the thing that a blog would announce or share publicly when your product comes out. Like, how would you want the public to see what you've built and then work backwards from there? I have tried to get models to write plans this way for a while, and none have come even close.
20:59 It has actually been quite frustrating. Fable can make the page look really nice, but it cannot write in a way that feels like an actual blog discussing a new feature. This was from the thread I talked about earlier where I was trying to add source control to LakeBed so that I could manage the code inside of the deployments so it was easier to make changes.
21:18 So I switched to Neon and I asked, "Do you have a good feel for the path here? Write up an HTML page describing the plan. Write it like a blog post explaining the feature. Post it on post plan, but ignore the style guides from the skill." There's a lot of edges here that many many many models get caught up on. There's only one question here and LLM love answering questions.
21:39 A lot of them cough cough openai cough cough would get really stuck on this question and focus on answering that rather than doing what I asked. I said it it should write up an HTML page describing the plan. Write it like a blog post explaining the feature. Then this is where things get real tricky. host on post plan which is my service for these files as well as in HTML skill that I have that describes how to do this and it also has some formatting guidelines in it but ignore the style guidelines from the skill.
22:09 This is a piece of this prompt that is ignored by basically every single model I have ever given it to. For reference, this is the formatting that I expect when I use this skill by default. And most models will steer towards this black and white minimal style because that's what the skill mentions in it even if I try to steer away from it. And here's what we got from Gemini.
22:31 Yeah, I sent this screenshot to Ben and he immediately was confused because not only does it look good, it also reads too well to feel like an LLM. Never lose a capsule again. Built-in source recovery for Lake Bed. You deployed a LakeBed app last week. Today you want to tweak it from a different laptop and you have no idea which machine folder or ephemeral agent work tree still holds the code.
22:56 Here's our tight implementation ready plan to make every owned lakebed deployment clonable by default with durable staging, strict access boundaries, and zero git ceremony. Bravo. Bravo. I am mad that no other model has written this well or handled this prompt this well. It isn't that hard. If Google could figure it out, the rest of y'all can. But like, holy [ __ ] Google figured it out.
23:15 One quick moment of transparency though. This does not fix all the Gemini isms. I simply don't care about the Geminisms anymore though because it's so pleasant to work with. So does it still hallucinate? Kind of. Still like bad enough. Like of its 72 claims in the TS Rust architecture analysis, 10 of them were wrong. That does put it slightly behind Fable 52 but slightly ahead of Fable 5.1.
23:40 Most importantly, 2x fewer hallucidations than Carbon, which already had overall 2x fewer than Argan. But I've also, as I mentioned before, lost a lot of faith in this bench because Astra did very well, even though the things it reports are garbage. And Fable 52 did mediocre, even though the things it reports matter. The other crazy thing to note here is that despite coming in at 13th place for its understanding of the TS Rust architecture according to my existing judging system, it was able to improve performance in
24:08 that repo the most and the fastest. So whether or not it is hallucinating about the repo, it is delivering. It is verifying its claims when it needs to actually implement. If you ask it about the repo, it will not do a very good job making sure everything it says is true. But when it comes to actually implementing it, it will get it right way more so than I ever would have guessed.
24:25 In my code review benches, it actually performed quite well, being admittedly slightly slow, but that's because I was running it on X high in a kind of butchered setup. It should be much faster now, but it also got 21 valid claims and five plausible that just weren't that important. Not a single wrong one. Very, very good signal to noise here compared to previous Gemini models.
24:45 So yeah, while I don't necessarily think this is the best bench in the world, when you aggregate all of the different things that I have been measuring for a bit now, you'll see here the Gemini 4 Neon has forced its way up from 12th place where Carbon was up to sixth place. It has massively increased its position in terms of the accuracy measurements that I do here.
25:08 But I don't care. I waited till the end here for this because I don't even think it matters because this benchmark does not reflect my real world experience. And my real world experience with this model is [ __ ] awesome. But now we need to go to fish slop because it is still not great at 3D. This is one of the hits you tend to take on smaller models and this seems to be like the hit it took the most aggressively.
25:25 It's [ __ ] up like the fonts and things here. It's not a good 3D model. Like this works. The movement feels fine. There's parts that are fine. Still not great. But I actually did two builds because I accidentally ran it on high initially. Okay, so I reran it on XI and the XI one's better. Still not great, though. This feels like a 56 soul to six Astra era.
25:56 Not like Opus 55 onward at all. It's definitely still behind the times compared to what we've been seeing with recent models, but I don't care. 3D is a silly thing. I almost feel bad for how much I have put this in my stuff in the past because it really does not reflect how the model behaves in day-to-day work at all. Unless you happen to be making like small 3D games for Twitter as a job, which sadly a lot of the influencers talking about models that is their job.
26:22 I write a lot of code like way more than most of the influencers do, way more than any influencer should, way more than most engines should. And this has been my experience. It is incredibly capable. It is incredibly coherent. It takes all the things I loved about Muse wonderful, turns them up a tiny bit, and then takes the capabilities of 62 Astra and other models, minus like the 3D and [ __ ] and makes them more coherent over long horizons and somehow delivers solutions faster.
26:47 It's just really [ __ ] good. So, now we are left with one important question. Where the [ __ ] did this model come from? As I've mentioned in almost all of my previous videos on Gemini models, the DeepMind team listens a lot better than almost any other team I have complained about in my life. The engineers in particular seem to have been quite frustrated with the state of things for a while now and they've been trying their hardest to fix it.
27:11 It seems like research started listening to them. From here, I am speculating, but there are parts that I know are true and I will be clear about those. My speculation is that the model training side of DeepMind in the research side of DeepMind was skeptical of how well engineering could give feedback on how to make the models better beyond like, hey, this is bad, fix it.
27:32 So research decided to try the things engineers wanted on a smaller model, not a super small one cuz that's not going to be good for engineering, but not a huge one because those training runs are super expensive and painful. And they had just done argan and carbon pretty close to each other. So another big model right after wouldn't make a lot of sense.
27:48 Even a medium right after would be a bit much cuz they just did hydrogen a few days ago and they just did carbon a week ago. So my guess is that this model was meant to be a medium-sized attempt to integrate feedback from the engine team. I do know for a fact it was not supposed to come out so fast. So why did this model get released so quickly? Again, this is a section I know is 100% factual.
28:11 Thank you to my friends at DeepMind for sharing this. The engineers at Google in DeepMind loved using this model so much that they begged and pleaded to rush it out because they wanted people to stop hating Gemini models so much. They wanted to know whether this was them going insane thinking this model was great and the world wouldn't understand it or if they actually had cracked something special here.
28:33 Well, I'll tell you with my full heart behind it, they cracked something special here. This is the first model to to make me feel a thing like this since since my first time with Fable. Opus was like a ramp up. Like I got more and more impressed over time. This model was instantly like slap in the face. It's different. And then continued impressing me more over time.
28:53 And they intentionally undersold it in the announcement for these reasons. The original tweet I saw was from Sundar, the CEO, saying, "This is our new mediumsiz model. We find it really good for code. You should try it out." And then I went and did. It's like, wait, no, this is not just like a medium-sized model for code. This is a a a generational leap for Google.
29:12 They do not have the balls to call it Gemini 5, but that's what I'm here for, to have far too much balls for far too little to back it. And I will loan my confidence to you for this one, Google. I will loan my confidence to you for this one. Deep mind, when you do the big version of this, call it Gemini 5. Just just leave for in the past. Wipe our slate clean.
29:32 Pretend those models didn't happen. It's for the best for everyone. Every serious person I know does not give a [ __ ] about Argan or Carbon. They are bad models. I have been struggling to convince the best AI and agent dev people I know to try this model because they were so burned by Argan and Carbon. Every time they do, they're like, "Wait, holy [ __ ] This is a generational gap.
29:52 The engineers felt it. Research wasn't sure. I'm a positive leadership didn't understand." But they [ __ ] did it. They made a model that is smart enough to do real work, is good enough at like staying focused in longunning long horizon tasks to complete really hard work and is coherent enough to stay on task and explain what it is doing consistently.
30:14 It's it's exceptional. It's a phenomenal model. I have to keep checking the calendar to see if it's like April 1st or something, but it's not. Like this is just a good model. They did it and you should go try it. Seriously, like just just go this one a shot. I I think the anti-gravity app is still kind of garbage and the CLI is fineish if you're okay with it doxing your email all the time and being slow and weird.
30:33 Obviously, I exclusively use it in T3 code and we are shipping a ton of fixes for anti-gravity in T3 code right now. If you do want to use anti-gravity in T3 code, I highly recommend the nightly because we are shipping fixes for it constantly right now because we want to have the best possible experience with this model because it is quite possibly the best model available for code right now.
30:51 You [ __ ] did it, Google. I don't know how. I don't know where it came from. I am thankful that you took all the feedback from the engineers internally and the ship posters externally and you took it to heart and you made something better. And I'm very thankful you made all the other fixes that you did over the last few weeks based on my crashouts because it would have been a lot harder to appreciate how good this model was if it was 3x slower than it had to be.
31:13 Remember this chart because we'll be going back to the capability coherency framing a lot going forward because I need y'all to understand this because the new frontier is not the capability frontier. The new frontier is coherency. And this is where OpenAI is currently behind some of the Chinese labs. And if you didn't understand why I liked Muse so much, now you know.
31:32 Combine the best of Astra, the best of Muse, and what you get is Gemini 4 Neon. It's a great model. I need to go make sure that my fever isn't back cuz I feel like I'm going insane. I have not experienced whiplash like this from a series of ball releases in my life. How do you make two of the worst large models I've ever used and then have 62 Astra come out and just break me because of how frustrating it is to use and then like right out of nowhere, Google comes back with a medium model that is the most pleasant and
32:02 enjoyable experience I've ever had coding with an agent. I don't know how we're here. I don't care though. I have a new favorite model and you might now, too. Go give it a shot. Let me know what you're thinking. And I cannot wait to see what they do when they put these new behaviors into the big version. This might be AGI. [ __ ] I I'm going to go mad if I keep going, so I'm going to stop now. Enjoy, nerds. Till next time. Peace. God, I can't believe they did