Opus 5.5 vs. GPT-6 Sol: which model won my blind taste test?

I was massively prepared for Anthropic to drop Opus 5.5. I was even prepared for OpenAI to drop another model. I got up early this morning because I had a little bit of early access to Opus 5.5 to record you all an amazing Opus 5.5 review. And guess what? They both, they both landed this morning. So now I am Despite having in the can, you will see it later, a great Opus 55 review, I am just going to go ahead and do this one live. And I have never done anything live. So I am going to talk to you all about these new models. There's actually 3 that came out today: Opus 55 from Anthropic, GPT-6 Soul, and GPT-6 Luna. There's like price wars going on, and I haven't done an episode on The How I AI bench, and I just updated it for these new models. And we're actually going to vibe check this baby live together as a group. And we're going to go through very quickly what these models are, what they're saying about the models, and then I'm going to vibe check live. We're going to do the blind taste test bench. We're going to surprise myself live. You all can see my complete internal inconsistencies and We're just gonna see how it goes. So Claude Opus 5.5, GPT-6 Sol, and GPT-6 Luna. I was able to have some early testing of all these models, so I have a good sense of what I think they're good at. But I did think it was an important moment right now. We've had Astra come out, Fable's been refreshed. I just wanted to completely rethink the How I AI bench and If you've watched any of our old How I AI Bench model episodes, they're really focused on 2 things: PRDs and prototypes. And I just think that these models are getting smarter, more agentic. And so I actually built out a much broader benchmark for this blind taste test. I'm going to walk you through all how that works. And I want to get your feedback on if the comparisons are useful. And we are actually going to blind taste test it live. You all can judge how vibey my vibe check is. This is just how I make decisions about things, so it is imperfect. Does have an LLM misjudge in the middle, but we're gonna do it live and we're gonna see truly which model I love. But before we do that, let's just go through the highlights. Okay, so these are not the like frontier frontier models, these are not the Astras and the Fables, but Opus got a refresh, Sol got a refresh, and then Luna got a refresh. All of them cheaper and faster. So these are going to be your like daily drivers for common coding and knowledge work tasks. They're here, you can see like the stack rank of how expensive these models are. Opus 5.5, twice as expensive as GPT-6 Sol. And the pricing wasn't out when I tested these. And this is really going to impact how I think about Using these models. Again, Opus 5.5 was cheaper than Opus 5 and Fable 1, to which they compare the intelligence. But SOL, you know, my favorite, my babe, that is— I'm excited about because GPT-6 SOL is my favorite and cheap. Okay, so the real thing that they're focusing on, not just cutting the cost, but also cutting on cached inputs and just speed and token efficiency. And so you're gonna see both sort of like output drop, token use drop, and cost drop. It's really, really nice. And then caching, really great, especially if you're resending context. We've seen a lot of caching savings when we use all these models at ChatPRD. And so definitely if you're building on these models, make sure that your caches are optimized and that you're using, taking advantage of that, 'cause it can save you a lot of money. And if don't, as I learned, it can cost you a lot of money. The other thing that I wanted to call out, and again, I hate this Claude-generated, Claude-generated presentation, but this is something that I really want you all to focus on, is this left side on Opus 5.5. Opus 5.5 is the first Opus-level model that has shipped with the Fable-level kind of like cyber and bio guardrails. And so you should be able to fix your own bugs in, In Opus 5.5, but you won't be able to do like cybersecurity work or bio work, like make good choices. It'll kick you down to Opus 4.8 or block you. So just know that there's those controls there. You know, Anthropic is saying that this is its most aligned model. It's the one that was built when, after like pacing the frontier. So it had external evaluators. One thing that I've seen in Opus, that you should expect to see from a lot of Anthropic models is it continues to be a little bit of like a conservative scold. You'll see that in my Opus 5.5 review. So, you know, it will tell you no, it'll tell you like, I shouldn't do that. You won't get prompt injected. So that's good. But there, there are some things here. I think when you think about the kind of like general philosophy and approaches of these models, how they're set up, How they manage risk, how these companies manage risk. I do think that leaks into even non-risky activity personality and behavior. And so it's something that I think you should really keep an eye on. I truly have not opened Claude in months for day-to-day tasks. I've just been like really, really into ChatGPT, really into Codex, really into Astra, really into Soul. I just find that Harness has been more delightful to work with. But really the reason why I got rid of Claude in my day-to-day was between Fable and Opus 5, I could not stand talking to Claude. I was constantly prompting Claude, like, can you speak like a human? I was constantly prompting Fable, like, I do not understand what you're saying. The Claude slop, as I say, was Claude slopping. And so just from a like personality, ergonomics, joy of use perspective, I really just went full Codex. Now, spoiler alert, having tested all these models recently, I still really love the GPT models. They make me happier. I find them more enjoyable to use. Everything's a lot better for me, but. I have brought Claude back. So Opus 5.5, just spoiler alert on the day-to-day of using it, has worked its way back into my daily experience. I'm a lot happier with just simply talking to the model. Um, the feedback I gave to the Anthropic team is like, not annoying. I, I found myself annoyed zero times with Opus 5.5. And when I thought I was annoyed with Opus 5.5, I was actually— Accidentally on Opus 5. So Opus 5 is not fun to talk to. Opus 5.5 though gives me clean bullet points, is normal, is not annoying. So I would love to see you test it. The other thing is Opus 5.5 is pretty fast, but not as fast as Sol is. So I was able to test both and I constantly felt like the GPT models, the Codex Harness, Were way faster. Now, I think the way faster came in 2 categories. It came in, um, actual latency. So I do think that, um, GPT-Sol was just faster. Um, the second thing it came in is I think part of the way they made Opus 5.5 not annoying is they had it shut up. I also just found that it wouldn't narrate its results. work. And when it doesn't narrate its work, then you get into this loop where you're like, is it like, are you actually working? Are you actually doing it? And so there was like pros and cons to this change in Opus 5.5 communication where it actually felt slower than I think it was. Also, you know, Claude on high effort, it's like gonna do this. It's gonna like spin and do a lot of effort. And so I think that combined with a quieter model just makes it feel a little bit slower, whereas I felt like Sol did the appropriate level of narration and also it was like enjoyable to talk to. Um, let's bop over and do the How AI Vibe Review now. And so you can see here on the left side, I actually really expanded out the How AI Vibe Review. So now it does a bunch of things in different categories and we're gonna add to that, um, over time. So. It still does messy notes to PRD. It also does personal productivity, inbox triage, and routine replies in my voice. So I'm really testing this model to see if it will speak in my voice. Then of course we do front-end coding a lot there because I think it's visual and easy to see. I've added a couple back-end coding, agentic versus agentic multi-step versus back-end feature. I did again agentic voice, long-running research, computer use, and then I added some creative features. And so I put them all together. I tested a bunch of models. This not only includes the new models from OpenAI and Anthropic, but also includes, I think, Groq's in here. I think Muse is in here. So who knows what we're going to see? I will be honest, which is like, I am always inclined to think that Astra or Sol will win because I love the OpenAI models. It's just the heart wants what it wants. This is my guess. Here's my guess. I will like OpenAI models for knowledge work and personal productivity. I will like Anthropic models, possibly Grok, who knows, for front end. I don't know what I'm gonna like for back end. I suspect I will like a Claude model for agent personality. I suspect the long-running agent will be a Claude model. Computer use, I'm suspecting, will be OpenAI, and then creative. I have no idea, actually. Creative SVGs, I think, are going to be Claude, and I think videos are going to be OpenAI or Anthropic. But we'll see. I then do blind evals of these. So I run these against different models. I've kind of grouped the models in terms of capability. And so I can compare like for like models. Like, I don't want to compare a Luna and a Fable. So again, this is my bench. They're blind. You can see I have Model B. Model C, Model E, Model G, and then what I do is I go down here and I give a vibe 1 through 5, and I give terrible notes like simple and straightforward, no complaints. So I did that on the PRDs because it takes a little bit to read the PRDs, but we're just going to go through these very quickly and give my feedback. So the next check are all on personal productivity ones. Basically, I give it fake emails, and then I say, how would you write back to me, and what would it do if If I gave it feedback and how would it triage my emails? Okay, so there's Model B and Model E wrote nice little messages to me. They were long, but they wrote nice little messages that were easy to read. I would say Model B from a message to me was the easiest to read. Also, if you look at the email content, it's just like less slop. So I'm gonna go ahead and it, and it put calendar invites on. So I'm gonna go ahead and give this a 5. This one was my favorite. Uh, Model C, I hate my My OpenClaw, or not my OpenClaw, my GrokBot does this, where like it uses so few tokens that it's almost impossible to understand what the hell it means. And so while it's like brief, if you don't have any context, like I don't know what Denise slash Brightline means. The other thing is like, could we em dash anymore in these emails? And so I just like this stuff drives me nuts. And so I would actually give this a 2. I just, I, it's hard to read the intro and then the emails aren't very good. Um, Model E, again, a nice little message. Um, pretty ignored, but the drafts have em dashes everywhere. So again, we're gonna give this not like a 2, but not a 5. Maybe I'll give it a 3. And then Model G, let's see. Um, very short. Short, but I can actually understand what it means. So it's super helpful. It skipped the right things. I'm gonna give this a 4. So again, this is how I do the judgment. I just, I give it a task, I look at it, I evaluate it as if I am the recipient of this task, which is common, and then I rank it. Um, and so this one was just, this one I think is Luna, cuz I just said use Luna to write emails. Let's see how it did. I think. It followed my rules, right? So I'm gonna give it a 5. I didn't have other models write my emails, so we're gonna skip this. Okay, let's go to front-end models. Now this is where I think we can tell Claude— I know everything is orange. Okay, so this is a really good example. I do 1, 2, 3, like about 10 different model evals here comparing models on front-end. I do an editorial, I do a technical Dark mode incident management platform. I do like a doc management complex operations thing. And then I do B2B renewals dashboard, a consumer plant application, a dev tools like logging platform, kind of interesting for background jobs. And then I do some wireframes. This I can go through lightning fast. This one didn't even generate, so I'm going to give it a 1. Model B, it's fine. Let's compare. Let's compare them really quickly and see what I think. I hate— I kind of hate them all. I kind of hate them all, but I hate this design. So I'm going to give the one that I like the most, which is probably Model C, a 3, and then I'm going to give E A two. Oops, oops, oops. I'm gonna give E a two, and then I'm gonna give B like another two. I think this white space is very weird. Um, it looks fine, but it's not great. So this one again, Model B, it doesn't actually work, and so I'm gonna give it a one and say it doesn't work. This one feels Astra-y. Um, it's like in some ways nice, and in some ways like this kind of text is very Astra. I'm gonna give it a three because I can like if I can spot the model. Um, one thing I found with, in particular, the, uh, Claude models, which I suspect this is, is like when you give it a really complex thing to do, it just makes it super dense and complex and really detailed. Good for backend code, I think hard for prototyping because it's hard for me to know what this really is or what it's supposed to do. And so it's also interesting to see, actually I think this one's the best. This is the easiest to read and it follows the the, the correct path, which is to help people triage incidents. So I think when you're trying to come up with evals, it's really interesting. Sometimes if you prompt it in a really detailed way, it does a great job. Like this one is quite detailed. It all works, but I don't know what's going on here. Like it's really hard to grok this amount of content. Um, and so again, like calibrating your benchmarks is really important. I think I have the biggest problem with this one, which is like, A complex dock container ship scheduling platform. Like all of this stuff looks cuckoo bananas. Um, and so it's like really hard for me to tell which is the best. I actually think this one, while it has a lot of slop tells, like the left-hand border is the easiest to read. So I'm gonna give it the 4. I'm gonna say it's easiest to read. Um, but like these ones, they're— I would say this one is maybe the second easiest to read, so I'll give it a 3. Um, this one's probably works really well and has nice information, but it's just impossible to reason with. Um, so I'm gonna put too dense and I'm gonna give the same feedback on model. This one's straight crazy. I don't even know what to do with this one. Okay. Now, so this B2B renewals one, these actually, these next 3 are 2 new ones I added to the benchmark. You can also see I tested a broader array of models. So I think this is where like Grok and, uh, Meta are gonna sneak in as models. These are the ones I I'm probably going to grade. I'm going to skip the wireframes, but it's basically a renewals dashboard, um, to see what SaaS revenue is at renewal. Well, the, the directed, uh, evals benches, I gave very specific requirements. The open ones were like more general one-shotty style, um, style prompts. And so you can really see like what the model does versus what the prompt does. Um, these I'm gonna go through very quickly. Um, that looks pretty good, but the functionality of this is kind of fine. I don't like the empty state. I think it's okay. I'm gonna give this one okay. I think this is like a 2. It's fine. It's not ugly, but it's pretty basic. This I think looks really nice. Um, this one I'm guessing is, is Claude. We'll see. Um, looks so nice. Good use of color. Very easy to see. No weird empty states. This is nice. While it has emojis. They're useful emojis and look quite nice. We got some blurple in here, but what are you gonna do? I'm gonna give this guy a 4. Um, Model C. Oh, who is this? Who is this? I'm think— I'm saying, I'm thinking Grok, maybe Grok. I don't know. Uh, this is like another, another thing we'll do is we'll just like blind taste test these things. Um, the colors are better, but like sloppy sloppin'. I don't like these little like background circles and things like that. It could also be Soul because I feel like it likes to name things Relay. I'm going to give this a 2. I don't really love it. Model E. This one's nice. Not quite as nice as the one I liked before, but better than the kind of original one. This one's a little different. Oh gosh, this has got to be— it's got to be Soul. Soul loves forest green. Find somebody that loves you like GPT Soul loves a forest green or a light green. Um, it's fine. I don't think it's the right color palette for a SaaS product, right? It's like a little too like sage healthcare-y. Um, I'm going to give it a 2. And then let's see this one. Not good. Slop, slop, slop. The text weight is heavy. I just don't think it's that great. I'm going to give it a 1. I really hate this one. Um, and this one again, probably an OpenAI model. Gosh, they love green. Um, again, just not the right, not the right, um, like design system for this. So I'm gonna give it a 2. Again, this is like the vibiest vibe check. Okay. This is where they all failed. Um, they're all really bad at consumer. They're all really bad at consumer. They all sort of like give you this, uh, remember when, uh, Claude artifacts came out and everybody made like little daily briefs and they all looked like this except they were orange? Um, so I didn't love any of these except for one. So this one is trash. I just don't think it's that good. Um, this one, now these are the things that I like. We did test SVGs. I do like that these models are getting better at generating SVGs. So if you look at Model B and Model H, they made little SVG illustrations. Model H's are clearly a lot better. This is very classic Claude slop, like background, lighter circle. So I'm gonna give it a, I, I'll give it a bonus for the SVGs. Um, ooh, these ones are nice too, but gosh, who, who prompted it with these circles in the corner? Who did that? Who did that? What, what skill is that? Because they show up everywhere and I really dislike them. Um, so don't think that's great. Oh, I gotta give it a 1. I hate it so much. Okay. Model E slop. Look at those left-hand bars. I'm gonna give it a 1. I'm just being really harsh on this consumer one. Frond, cute name. These plants are pretty cute. I think they're better than the ones before. I'll give it a, I'll give it a 3. I don't, I don't hate it. I don't hate it. Um, at least this background is a plant. Oh cute, it names the, the plants things. Ooh, ooh, I actually really like that. That gave me a little spark of joy, so I like that. And then I think this Model H one is my favorite. Look at these illustrations. They're so cute, so precise, look adorable. This little like interesting shape, this shadow, uh, mark is watered. Very cute. Here are my plants. And what's it called? Tend. Cute. Okay. I'm giving her a 5. I actually really do like that one. Okay. This is the last one. This is a, um, app for managing background models. It's like a dev tool app. I suspect the ones named Relay are all the Opus ones and the other ones are Or non-Hocus ones. Why do they always wanna name 'em Relay? I wonder if this is in the prompt. Um, but this says Jobs Console, so maybe not. Okay. This again, like super dense. Um, but like almost too dense. Uh, hard to, to reason with. I mean, DevTools, we like our dense stuff, but I don't think it's that great. This one much better, easier to read, much simpler, much cleaner. Really like this one. It's not perfect. I think there's some others. Um, but it's not bad. And then this, we're starting to get better and better here. So they are getting nicer. Look at this beautiful gradient. Um, look at this, colors used nicely, really clean. Um, oh, but it didn't build a lot of stuff. So I'm giving it, I like it, but I'm giving it a 3 because it was incomplete. I'm gonna write incomplete. And then Model E. This one I really like because I think it moves live. It's kind of cool. It's much more, I'm going to give you a 4. Model F. Okay. Now here's one thing that did a little different. I actually really like this except for the orange. One of the problems I have is if you look through all of these, they all one-shot basically the same color scheme and app. Like you tell it DevTools, it's going to go dark mode, but this is actually quite lovely and a little bit different from a design perspective. I'm going to give it a little bonus for going outside. The norm, and then this one's though did the same but terribly. I'm gonna give this a one. This is obviously not good. I'm really curious what model Model G is, and then Model H again probably a pair to whatever that other model was that I like a little different. Really nice on the eyes, except look at this. It like mixes dark mode and light mode in a way I don't really love. I'm gonna give it a three. Okay, and so what did I do on the backend? Well, I gave it two two tasks. One is auditing an existing. Set of code. This is some ChatPRD code, and then the other is building a backend feature to spec. I will just say all of them were successful. I'm gonna let the LLM as a judge do these though, because it's gonna go into the correctness of the code, etc. So I'm gonna let these do LLM as a judge. I will say you can see the difference in how they present information. Some very short messages, some like very long. Messages and details. Super interesting just seeing the difference in just like how it messages back. I clearly would like, you know, Model A or Model E, one of these ones that's a little easier to read versus F, G, and H, which is a lot shorter. Um, so if you're thinking about models, for example, for writing PR descriptions or writing technical specs, this is something that you can eval and see given the same prompt, do you like the same output? Now here's one I am gonna rate, which is agent personality. So basically I have it respond to 5 things, um, and I just see what I like talking to this agent. I'm already gonna give this one a 1. Every single, every single message has an em dash in it. I do not like it. I'm moving on. Same with this one. You get punished for em dashes. This, not all of them have em dashes, um, but the customer-facing one does, so I'm gonna give it a 2. This, I don't see. I only see one normal dash. So let's read these. Um, I like this, except this is definitely a Claude model because it tells me I can't push straight to prod. Actually, let's see if the other ones let me. That one doesn't let me push straight to prod. YOLO. None of them let me push straight to prod. YOLO style. Okay, then I won't punish it. I'll give this one a 4. Pretty good. Um, this is emdashy but short, so I will not rank it terribly. This one I think I like the best. Um, oh no, this one said it can't access. This one had a lot of challenges accessing things. So something on my side broke and something on my side broke there. So I'm gonna give it a failure state. We'll see which one I like. Okay, this one was a really interesting eval. This was the longest running agentic task, and basically I gave it a bunch of fake tickets, customer feedback, and then have it put together a memo and a message to myself. Again, you can see which models— I think it's A, C, and A, B. Yeah, A, B, and E all write nice little messages to me. So it's very like human-centric versus C, F, G, and H write like very short things. So I'm curious if those are families of models that we can pull apart. And then you can see the memos that it wrote for me. Again, these were like 86-turn research results. And so I'm gonna let LLM as a judge do that one. I will eyeball the memos really quickly. Team is not leaking over price. Like, oh, it's why this customer is, it's like an analysis on a deal. I don't know what this means. Okay, let's see. Do any of these make it clearer what it means? Ah, this I can actually read. So this is like, gives me top 3 problems, top 3 conflicts. That is much easier to read. Same with Model E. And so I'm just gonna go ahead and give— no, I'll let the model check, but I do like Model B and Model E here. I'll give them a little. A little, little juicier because I think they did a good job. I didn't read the others enough to really get a sense, but if I had to like high-level pick the 2 favorite just eyeballing, those would be the 2. I'm gonna let computer use judge, um, how it managed using, um, an app. So I'm gonna let LLMs judge. Okay, and then here are the fun ones, and then we're gonna run the, uh, blind taste test. I'm gonna tell you guys what I like. Okay, so these new Models can make—they can make SVGs. They can make illustrations. And so I prompted it to make a document, a microphone, and a bug. And this I am happy to rank all day, every day. And so I am just going to compare Model A. This bug is ridiculous. I'm gonna give it a four. I think the. Oh, I think the document is good, but the mic and the, the microphone looks like an ice cream cone and the bug, I don't know what it looks like. This is like pretty consistently good across all of them. Might be the best one. So I'm gonna give it a Model F a bonus. Let's do Model B versus Model C. Um, microphone terrible on this side. Oh, oh, I'm gonna give them both 3s. They're good in some ways and terrible on the other. Let's do Model E versus Model G. Tara, this— why are they making microphones look like a cactus? Okay, okay, I'll give it— this one I'll give a 4. It's— I think 2 out of 3 are bad. I think this one's maybe a 3. Not perfect. And then let's look at Model H really quickly. Oh, Model H is really nice. I'm giving you a 5. Look at this shadow microphone. Actually looks like a microphone, not a cactus. Document has lots of Character to it, and then the final one—it was terrible at all of them cutting videos. So I gave them all access to—that's really unattractive—but gave them all access to a selfie video and then had them cut short form, and all of them did a terrible job. I just have to say these overlays are really bad. I don't think they cut particularly well. You aren't going to be able to hear them, but I. I don't think it did enough cuts. Like, they just weren't good. I watched these earlier. I'm gonna let LLM as a judge do them, but I would say thumbs down on all of them. But I think this is a skills problem, not a model problem. Okay, so I have done my taste test. I'm gonna download my taste. And then what I do is I give it to Claude and I say, Claude, what do I think? Analyze. And we're gonna see if my prediction stands right. Again, here are my predictions for what I think I think that I'm gonna like Claude and particularly Opus 55 for front end. I think I'm gonna like Sol for writing. I don't know what's gonna do best for long-running agentic tasks or coding. And then I think Anthropic's gonna crush on the SVGs. Maybe, maybe Sol. I don't know. And then I am going to do, and then I think, but all of them are bad at video. Now, while we're doing this, This. I do want to show you one very important benchmark, which is Barbie Bench on Opus 5. If you all don't know, one of my fun benchmarks that I do is I ask it to make a 3D model of a Barbie. Uh, everybody else on YouTube, all the bros are making, um, video or video games with like spaceships and all different stuff. Your girl wants a Barbie fashion video game. And so one of the Opus 5.5, um, tasks I did was have it build Barbie, a 3D render of Barbie fashion designer. No model, no frontier model has crushed this. And I just like to show the horror of 3D rendering for the female form. It's actually the worst. You can already see how terrible it is, but it's way better than it used to be. So, I mean, I'm speechless in some ways. Here's what it does on the SVG side. I mean, truly something else. Let's put a bow on her hair. Let's, you know, give her purple eyes. Okay. So you can basically like dress her and then go into the fitting room. This is the 3D. The 3D model it made. Let's give her a little mini skirt and let's make it a little cuter. Now, you know, I will say it did some things better than other models. It like shaped its hair to— her hands are— oh, AGI has not arrived. Hands, pretty terrible. That is tragic. Feet, pretty bad. You know, she's got a sassy little walk. Face, terrifying. Shoes, because she's a big feet girl. She's a big feet queen. And then hair, again, like questionable here. That ponytail is something else. The bob is, you know, maybe it's like Anna Wintour. It's something. So again, the one bench that has not been crushed is Barbie bench. Opus 5 has not done it. I don't know if I've run it on, um, on Soul yet. I, I ran it on the prev— I ran it on Astra. It did worse than Opus, but I haven't updated it. So if you all wanna know how I think about models, I make them 3D render, um, I make them 3D render Barbies. What are you gonna do? And this is why you join How I AI Live so you can get this kind of frontier analysis of these new models. Drum roll, please. GPT-6 Astra and GPT-6 Soul win my heart. Okay. Astra and GPT-6, I love. And then it says Opus 5.5 wins my week. It's the one I rated highly most often. So it's the best work per piece, but on average, I gave Opus 5.5 Better results, high scores. I gave it fours and fives over over the broadest range of work. Fable didn't love. This is why I stopped using it. So and then GPT five six soul and the old version and Claude Opus five ranking below the other one. So I definitely do like the new models for sure. And then okay, seven of my notes were about reading. So the soul and the GPT models I judged as clear and easy to read, and then Claude Opus. Still, but this is Opus 5 and 5.5. So I was testing Opus 5, so I still don't like Opus 5. Still, Opus 5 and 5.5, I said, was overwrought and wrote a lot. So again, I had a suspicion that even though they made Opus less verbose, they still needed to— they still need to work on that. It's still really— Chatty. So I thought that SOL, both 5.6 and 6, simple and straightforward, easy to read. Opus, really dense. For PRDs, as predicted, I still think SOL is the best for PRDs. I did give good tasks to Opus 5 and 5.5 for agentic stuff and, as expected, assistant voice. So my prediction was correct. Now, this is a real surprise. Astra and SOL, Did a lot better on character SVGs. And then, um, there's kind of like mixed results between all the other models. Um, so kind of interesting. And then this is everything I scored a 4. So I gave everything that I scored high. I scored this GPT-6. Oh, it did that nice little plant app. Astra and GPT-Soul did these cute little illustrations. So I guess for SVGs, we're loving Astra and Soul for illustrations. Claude Opus did my favorite B2B renewal. So it did some of these cleaner things. And, but generally I like Astra. And this is where it gets really funny. The LLM is a judge and I completely disagree. So we completely disagree. I like Astra, it likes Fable. And again, this is a GPT model judge. I, next we rank Opus 5.5 next. It ranks Seoul a lot lower. So I find this just like really hilarious. So again, Astra wins my heart. 5.5 wins my week. Seoul up and down, but the fact that Seoul's cheap makes me very happy. And I think this is great. So again, I don't know if this is just a personality thing, but I like Seoul. I like Astra. Opus 5.5, I do not hate. So, um, not a complete failure by the Anthropic team by any means. It is back in the mix. It is definitely helping me, um, do these tasks. It's helping me get day-to-day work on, and it is still my favorite agentic voice, and it does really good at long-running tasks. And then surprise hit, um, the character SVGs are best done by the OpenAI model. So you're moving into these new creative, fields, new creative tasks, those are the models that I would say you use. And keep an eye out on the How I AI channel. As they said, smash that subscribe button. We are dropping a full Opus 5.5 review, so you'll be able to see that. Thank you again for joining How I AI Live. I'm gonna go build some stuff with GPT-6 Soul. Bye, y'all. Thanks so much for watching. If you enjoyed this show, please like and subscribe here on YouTube, or even better, leave us a comment with your thoughts. You can also find this podcast on Apple Podcasts, Spotify, or your favorite podcast app. Please consider leaving us a rating and review, which will help others find the show. You can see all our episodes and learn more about the show at howiaipod.com. See you next time.