Загрузка видео...

Не удалось загрузить видео

На главную

Claude Code vs Codex vs Grok Build: Who builds the best Windows 95 OS in HTML? I benchmarked them live on speed, lines of code, file size… and actual usability. Claude: Fastest (384 lines, 14KB) but basic Grok: Took longer… and built a monster (full Explorer, Paint, interactive Grok...

44,585 просмотров • 2 месяцев назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

I just compared Claude Code vs Codex vs Cursor CLI The task was to build a Next.js app with Tailwind 4 and shadcn components to collect customer feedback and showcase it with a widget. I gave all three the same prompt and let them go for 30 minutes to see what they came up with. Claude Code with Opus 4.1 Even though I told it to set up the app in the existing project folder, it tried to create a directory for it. After I interrupted and told it not to do that, it built a demo form and landing page with no errors. I had to ask it to make the demo interactive so users could submit a testimonial and preview it. The landing page looked like AI and was pretty basic, but it worked and it was done in a fraction of the time of the others. Total tokens used: 33k Codex with GPT-5 At the end of the 30 minutes I just could not get Codex to produce a working app. It got stuck in a loop of not being able to set up Tailwind 4 and despite many, MANY, attempts, I ended up with a "failed to compile" error. Total tokens used: 102k Cursor Agent with GPT-5 This was the slowest agent by far and a couple of times I actually thought it got stuck in a loop and was close to Ctrl+C'ing to cancel it. The TUI is really nice though, especially how it shows diffs and it did eventually build a working app (after one or two slight errors that needed fixing) The demo was interactive and it had a very minimal design that looked bare but also a lot less like an "AI generated" app than the Opus 4.1 design. It also wasn't too chatty and just did what it needed to do! Code quality was on a par with Opus 4.1, but it did use 5.5x as many tokens to get there. Still cheaper than Opus on a direct comparison but not when you factor in a Claude Code Max subscription. Total tokens: 188k I'll be able to do a proper comparison and record some videos when I'm back from holiday but for now, Opus is still the more capable model out of the box and Claude Code is the more complete CLI product. It will be interesting to see how Cursor evolve their CLI though with commands and subagents because I think with GPT-5 they have a real shot at providing competition for Claude Code if they can optimise output to get similar quality with less tokens. Jump to 0:40 in the video to see the two apps. Which do you think is which? ;)

Ian Nuttall

194,949 просмотров • 1 год назад

⚡ My first advanced simulation with Grok 3! Finally your OS windows act like REAL windows 🤣 As you know, I've spent more than 2 years sharing all kinds of simulations and mini-games made with Claude, ChatGPT (o3-mini-high), etc. It’s been ages since I last wrote a single line of code. But pretty often, once you hit over 1,000 lines, it turns into a debate against the LLM and you frequently get stuck in a loop that’s hard to break out of. Everyone was raving about Grok 3’s ability to generate code, but until now, I hadn’t really put it to the test. So I decided to challenge it with a prompt that both ChatGPT and Claude were seriously struggling with (debate loop). The initial prompt was: "Use Python and a 2D physics library to create a world where I can generate different static objects like squares, triangles, circles and rectangles. I should be able to move them with the mouse, rotate, scale, and delete them. The cool part is that we’ll see this world through 1 to N operating system windows. In other words, the windows will be like real windows! When one of these windows is active and I hit the spacebar, balls affected by physics should appear and interact with the static objects. You can start with placeholders, but later I'll send you a series of PNG images so they all become beautiful sprites." After a few iterations, I got the result you see in the video. Insane, right? 🤯 Now, with Grok, we have the power to create anything that pops into our mind with just a couple of prompts. It’s mind blowing. Ever since I was 9 and messing around with BASIC on my MSX, I've been hooked on visual simulations... And now I can create them using nothing but natural language. It's f***** amazing that we're living in this historic moment!

Javi Lopez ⛩️

209,470 просмотров • 1 год назад

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:

Steve (Builder.io)

42,501 просмотров • 1 месяц назад