Less Bitter · Transcript · · Updated
Claude Ultracode is super intelligence. – Transcript
Video by Less Bitter · Watch the original on YouTube
Summary
AI-generated from the transcript. Verify details against the source video.
- The speaker used Claude on Ultra Code to build a 2700-line spec end to end in about seven hours.
- Ultra Code automatically spawned critics, reviewers, and skeptics to review the spec and implementation without human instruction.
- The speaker argues that agentic coding and automated testing yield higher build quality than human-driven development.
Use this video with Pro
Reading, copying and transcript downloads are free. Create saved AI results for this video with a signed-in Pro account ($9/month).
Transcript
Search ignores accents. All transcript text stays visible.
Let's say you had this spec here. This spec is 2700 lines. And imagine you gave this spec to a general purpose human being, a general purpose engineer who has some experience in your codebase, but you know, it's kind of like a new hire. How long do you think this would take him to build? I mean, first of all, how long would it take for him to read this? A couple days to wrap his head
around it. Needless to say, this would take a human engineer, I don't know, three months to build this out, if even possible. I don't know how. I mean, I don't even think a single person could handle this spec because first you'd have to read the spec, then you'd have to break it down into projects in parts.
Now, the question is, could an AI pull off the implementation of this spec? And the last time I had an agent try to do a spec was back in like March of this year. And it failed catastrophically. It failed so much that I dedicated my life to tearing apart the scam of AI coding.
I'm like, dude, what is this Like they promise you that the agents could do all this and that you back in March you gave the agent a spec like this. It wasn't even this long or detailed. It was maybe like a 500 600 line spec and the agent would be like say less bro I got this and it would go and it would just drown in its own vomit and leave your codebase an absolute mess and it would just give up and it'd be like done
and you'd be like did you finish? It's like, "Oh, I finished." All right. You know, finished what the turn, right? It's like, I finished processing tokens. Did it finish the feature? No, not even close. Did it leave your codebase in a functional state? Not even close. And so, back then, smart engineers would face these little hurdles and be like, man, I got to design systems for these engineers so they can get through for these AI so they could get through these
specs. Now, as you may have seen, Opus 5.5 in recent videos has turned me into somewhat of a believer in the coding um completion part of AI agentic engineering. I've seen it able to do things it wasn't able to do back in March when I was when it was the last time I was working on a serious project.
Now, I'm working on an app called Enjoy and I'm doing this fully agentically. You may call it vibe coding. I call it evolutionary coding. Okay, you you let the code evolve to satisfy environmental pressure, which is the tests and if it works, if it passes those pressures, then you let it proliferate. It's like biological genomes are an absolute mess, but they work. So enjoy. This app lets
you use AI coding agents that are on your computer, the terminal ones. It brings access to these terminal agents that were otherwise prior reserved only for like developers who knew how to use a terminal. Now anyone can access these. And as I was talking with a few people, a lot of them said, "Man, I have a like a non-technical co-founder that I'd love to share my project with. It would be cool if we could collaborate together."
Anyway, long story short, I needed to go in with a whole new redesign of how the teams feature worked. I was dreading it, man, because it was big. It was huge. It was like changing everything, right? It's like we built the app one way and now we had to change everything to make it multiplayer.
And if this was any other era, if this was 2020, this would have been a 3, four month project where I would have just had to stop everything I was doing, go hide in a cave for three or four months, not shower for weeks, and just wallow and drown in technical misery. And so, um, you know, I started with this huge voice memo, just thinking out loud in terms of how it should all work. You
know, I just worked with it through Claude and it went ahead and it built this spec, right? It started with this spec. And I was like, "Oh, you built a spec, did you? Okay, well, what the do you want me to do with a spec?" Because the last time I gave you a spec, it didn't end well. And I opened the spec and it was this spec and I was like, "Oh my god, dude. Holy sh. You're telling me, Claude, that you're going to be able to build out the whole feature
according to a 2700 line spec? I was just like, "Oh, I'm so screwed. This project is screwed because I don't know how I'm going to build this. This needs to be built." And the last time I tried to do something like this, it failed.
And I had to go in and take this spec and divide it into 10 little man maybe 20 little manageable pieces that an AI agent could do. And it was just no fun at all. So, I was like, you know what?
Let's try. Let's try. So, I put Claude on Ultra Code. Uh, effort level Ultra Code. If you don't know what Ultra Code is, it's like a nuclear the nuclear option of Claude. This thing will spin up 80 agents, man, to do your work.
It'll spend an ungodly amount of time. And honestly, I'm still I'm on a $200 plan. So, so I just said build the whole thing end to end. I put it on Ultra Code and it said on it I'll build the full computers and devices model across the relay. So this was at 3:20 p.m. I guess it worked. Uh it ended up working about 10 hours. And so about an hour later I was like have you done any work yet? Why do not I not see any changes or commits?
So it was writing the spec, the 2600 line spec. An hour later I was like why still no work done? It says you know uh I it spawned four critics to review the spec. uh 5:24 wrote the spec by 8:00 PM had done a couple commits by 8:15 I saw that it had 60 agents working and I'm like oh my god either this is some infinite recursive bug that spawn is spawning like these were hacking
hugging face or some and it was like most of those are the reviews skeptic checks now I didn't tell Claude I didn't tell it how to do this um Ultra Code just spawned its own skeptics and adversarial ial reviewers to review the spec to review the implementation. Eight reviewers produced about 34 findings so far. Before anything gets fixed, each finding is handed to two or three independent skeptics who try to disprove it. Three for high severity findings,
two for the rest. Again, I didn't tell you to do any of this. This is just the way Ultra Code works. That adds roughly 80 short readonly agents on top of the eight viewers. 823 so far. 45 of 53 agents have finished. Okay, 9:55.
It looks like it finished uh by 9:55, I guess. And the question is, so this was the whole spec. So, you know, from 3:00 p.m. to 9, let's say 10, that's 7 hours.
7 hours to build this spec. And did it do it correctly? It did. It did, man. Dude, not only did it do it correctly, the end result was flawless. It's like everything just worked. And this is a very complicated flow here that involves pairing like a phone and a a web browser to the desktop client, coordinating between a relay server, end to end
encrypting the traffic. So in 7 hours, Opus 5.5 built this whole spec and it did it correctly. Now you may be thinking if you are somewhat of a skeptic, okay, sure it works, but what about the code quality? It's probably all slop or end to end encrypted.
Yeah, okay. How could you ever trust that? Here's the thing about the current generation models that I see. If they tell you something, I it is pretty high confidence. They are pretty skeptical. They do not trust themselves. So, they always doublech checkck things, triple check things. And so if you ask it and you put it on a high enough effort level, does your implementation meet the
spec, it will answer that accurately. This whole idea of hallucinations is is not something that you see anymore. The models are pretty good at admitting that they're uncertain or unable to attain certainty. And so I'm sharing this not because I want to hype up AI, but I want to tell you that it they
fixed AI, man. They fixed it. Like I'm amazed because the thing that diselusioned me from AI back in early of this year was its incapability of not only the inability to build out specs, but lying about it too and saying, "Yeah, I'll build out the spec." And just and just faltering completely. And
now I don't know what they did, but it's it's able to work for like 10 20 hours and not lose the thread and not devolve into incoherency. And I just didn't think that was possible. I didn't think like dude, look, I don't know what AI is. I don't know what if we're calling it intelligence, pseudo intelligence, next token predictor. I don't know what it
is, but it is able to go through this entire spec and build it end to end with an insane amount of tests with an insane amount of fidelity to the spec requirements. Yeah, I don't know what to call that. Um, if not like beyond intelligence, you know, I can't even assign a date to how long this would take a human being. Honestly, I just I don't even think this is possible for a human being to do in any reasonable amount of time. Not one human being,
maybe a team of like 10 of them meeting up, breaking this thing apart, man. And dedicating their whole lives to it for like three months. That's what it would take. And Claude did it. It didn't even kill my 5 hour limit on the $200 plan.
It didn't. Yeah. Look, this video is just to catch you up, man. Is is to is to share with you the things that I'm seeing. Look, I I have been um I've I've oscillated a bit with my videos because I always loved AI in theory, but I was always disappointed in its execution.
There were two videos I made back in March. One was a video about Cloudflare, uh vibe cloning, vibe forking Nex.js, and the other one was called like I was a 10x engineer, now I'm useless. In those videos, I talk about evolutionary coding. I'm like, wait a minute. Nature builds us somewhat blindly, right? It tries things and if they pass the test, which is the sort of evolutionary
pressure, it keeps that feature and it passes on. Meanwhile, DNA, the genome is junk, like it's filled with junk. It's it's or gunk, let's say. If if your criticism of AI building things is it's all slop, it's all junk, I got news for you, man. Well, you know, what do you think all this is? Now, I don't want to insult like your religious