Loading video...

Video Failed to Load

Go Home

BREAKING: GPT-5.6 Sol is out—AND Codex has been merged into ChatGPT Desktop as ChatGPT Codex. This combo model and desktop app harness are the gold-standard for knowledge work in AI. 5.6 is powerful, fast, half the price of Fable, and my default for almost everything. We’ve been testing it...

140,781 views • 2 days ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

BREAKING: GPT-5.5 "Spud" is out and it is a BEAST We've been testing it Every 📧 for the last 3 weeks on everything from coding, to writing, to knowledge work. Here's our day 0 vibe check: - It's a step change in coding AND it's easy to talk to. It's fast and friendly and quickly became my daily driver. But it's also a coding powerhouse—a really rare combination. - It scored 62/100 on our Senior Engineer benchmark. Opus 4.7 scored only a 33/100. (But GPT-5.5 performed best when using an Opus 4.7 plan). Naveen Naidu used over 900 million tokens during testing—and it let him ship production features for Monologue at both high speed and quality. - It has serious conceptual clarity. It can hold a complex plan in its head over hours of work, without getting distracted by existing code. This makes it the first model that we've tested that can perform well on complex refactors requiring deleting and reimagining an substantial existing codebase. - It's a very good writer. This is the first OpenAI model in about a year that got our writers Every 📧 to switch away from Claude. 5.5 has Katie Parrott's seal of approval—not an easy task. Its writing feels more organic and it's better at mimicking a writing style without going overboard. - It's great for agentic knowledge-work. This is the first OpenAI model that manages to be both a stellar senior engineer AND that can be used for everything from spreadsheets to research. It's crazy fast, and it's amazing inside of the Codex desktop app, and got much of our team to switch away from Claude Code and Cowork during the testing period. However, it's not a perfect model. - 5.5 still loses to Opus 4.7 on plan quality. It's plans are extremely readable but Opus has better attention to detail and sharper insight. - 5.5 still loses to Opus 4.7 by a bit on front-end and full-stack product work. Kieran Klaassen found that it wasn't quite as good when full-stack thinking and design are involved. And it's not great writing Ruby. - 5.5 is a great vibe coder but if you're vibe coding without a plan it's worse than Opus. Mike Taylor found that Opus is better at reading in between the lines on underspecified vibe-coding tasks. Overall GPT-5.5 is a massive achievement from OpenAI and it deserves a serious look as your daily driver. Read our full vibe check on Every 📧 here:

Dan Shipper 📧

130,236 views • 2 months ago

GPT-5.6 vs GPT-5.5 on my custom spaceship prompt. I gave both models the exact same custom prompt. This is also the same prompt I previously gave to Fable 5. For context, GPT-5.6 Pro worked for 87 minutes, while GPT-5.5 Extra High worked for 34 minutes and 42 seconds. As I’ve said before, based on great authority GPT-5.6 will be an incremental/soldi improvement over GPT-5.5, not a “Fable killer.” My rough expectation has been that it would trade blows with Fable 5 on some benchmarks, maybe win around half depending on the category, but not clearly surpass it overall. And again fable five will have bigger model smell, but this was expected. After testing this coding output, that view feels pretty accurate. GPT-5.6 is clearly better than GPT-5.5 in several visual areas. The lighting, shading, chairs, object details, and exterior of the spaceship looked noticeably stronger. The scene was also easier to test. I do want to give GPT-5.5 credit though. It built out the rooms much much better and the planets looked better than GPT-5.6’s. It was also interesting that both GPT-5.5 and GPT-5.6 produced better-looking planets than Fable 5 in this specific test. The downside with GPT-5.5 was stability. The game was much glitchier and harder to test compared to GPT-5.6. But when it comes to the core of the demo, which is the spaceship itself, Fable 5 still beat both models pretty comfortably. GPT-5.6 is impressive, but from this test, it looks exactly like what I expected which was a meaningful incremental improvement over GPT-5.5, at least for indie game demos, but not something that replaces Fable 5. In collaboration with Chetaslua

Chris

228,126 views • 22 days ago

I’ve been using GPT-5.6 Sol internally for the past two months, I've spent probably 25+ billion tokens. Here’s my review and comparison to Fable 5: > Let's start with the analogy because everyone seems to be giving theirs - GPT-5.6 is likely the last version of the GPT-5 training run series. It's kind of like an athlete at their peak. Through years of experience in the game, they've become the most reliable player and has the highest game IQ. But, there's no more room to grow. Fable on the other hand, being essentially the first version of a new training run, is the first round draft pick rookie. Raw talent mixed with the energy only a young person would have results in some incredible plays we didn't think possible, but also mistakes due to lack of experience. But that rookie will only improve and likely will be better than the veteran ever was because it's a new game and a new era. > GPT-5.6 is genuinely better at long, sustained work. With /goal, I've had it running complex projects for days with almost no intervention. It built a Minecraft-style game, kept adding features and mobs after the core game worked, and only stopped because I stopped the run. I never felt as though I had to jump in and guide it back to the right path. > It keeps finding useful work when you give it a concrete finish line. I had it recreate Excel with a loop. It inspected the real desktop excel app with Computer Use, comparing that against its own build, and closing the gaps. I stopped it after six days after it had built an incredible amount of functionality. > It's faster than other models in two different ways. The raw generation speed is higher, something OpenAI has been putting effort into. But it also takes a shorter path to solutions. It wanders less, changes less code, and generally knows how to get things done directly. In daily use, it feels about 2-3x times faster than Fable. That's my impression, not a controlled benchmark. The difference is large enough that I notice it constantly. > It works well across a wide range of tasks. I use it for one-line edits, quick questions, browser chores, and multi-day builds without changing my prompting style. Speaking of browser control, its the best ever I've used. To the point where I actually use it often. If a task lives on a website, GPT-5.6 usually opens the browser and does it there instead of asking for an API key or forcing everything through the terminal. When I switched back to GPT-5.5, it went straight to the command line even when the browser was clearly the better tool. > And it can handle real browser work, not just toy demos. During a data import, I had it monitor Supabase and resize instances as the load changed. It stayed on the dashboard, adjusted capacity, and checked the result without an API or a custom script. > I also gave it a full Google Workspace migration. It moved Forward Future from to preserved the old aliases, and configured MX, SPF, and DKIM. Before a consequential save, it stopped, explained exactly what would change, and waited for confirmation. > The reasoning setting matters a lot. Light is good for questions and small edits. High and Extra High are the sweet spots for serious work. Ultra usually takes longer than the extra thinking is worth and burns tokens. > I love that 5.6 is split into 3 sizes. Not only can you control speed and cost that way, but you still also have the thinking effort setting for each of them. Very precise controls. I just wish Codex automatically routed my prompts for me. > Its personality is blunt and a little bland. Claude feels warmer and more natural to talk to. GPT-5.6 is more clinical, but I like that for work. It gives me enough explanation and rarely pads the answer. I usually have to ask Fable to explain things more simply and/or more concise. > Its front-end taste has improved, but the default is predictable. Left alone, it turns websites into PowerPoint decks with huge statements and hard section breaks. The good news is that it takes design direction well and can revise without destroying the parts that already work. > It still makes confident mistakes. I asked it to rebuild parts of a system, and it told me the job was finished. Later, I found out it wasn't. Bits of its internal process also leak into the answer occasionally. > Claude Fable is more naturally autonomous on large, open-ended projects. GPT-5.6 is easier to reach for. I don't need to invent a huge project to justify using it. It works just as well for a small edit or browser chore. > GPT-5.6 is also cheaper. Sol costs $5 per million input tokens and $30 per million output tokens. Fable costs $10 and $50. Cached input is cheaper too. Still, cost per finished task matters more than cost per token. > GPT-5.6 isn't the best at everything, and it still needs supervision. But it generates faster, wanders less, works at almost any scale, and wastes less of my time. It's the model I have the most confidence in to get the job done right the first time. I put together a full breakdown with all the tests, prompts, and examples on a site. You can read it here:

Matthew Berman

179,362 views • 2 days ago

BREAKING: Anthropic just dropped Claude Fable 5—this is Mythos, made safe for public release. It is the best coding model in the world. We've been testing it internally Every 📧 for the last week or so across coding, writing, marketing, editing, and more—here's our vibe check: - It broke our benchmarks. Fable scored a 91/100 on our Senior Engineer benchmark—this is human senior engineer level. The previous high score was Opus 4.8 at 63. GPT-5.5 is a 62. - It's a one-shot wonder. You can set it and forget for hours or overnight on huge coding tasks, and come back to completed work. It cleared entire production bug backlogs, built a playable 3D, and even made a 2-minute animated film—all one-shot. - Taste and attention to detail. In coding and knowledge work tasks, it has much better taste and attention to detail than we've ever seen. It gets subtle things right, adds little features you might not have thought of, and generally understands the assignment in ways that surprised us. - Great use of context. We set it loose analyzing customer feedback surveys and our website data and it came back with a crisp, clean report that identified a. our biggest problem and b. a concrete testable solution—and then we sent it off to build that. - It's best for power users. If you're already used to orchestrating multiple agents in your work, this model can do things that you've never seen before. If you're a knowledge worker or vibe coder with a more basic setup, you're not going to notice a huge difference—in fact, it probably isn't the right model for you. - It's very slow, token-hungry. Using this thing for regular knowledge work is like squashing an ant with a rocket launcher. It also routinely uses 500k to 1M tokens on tasks. That's why it's best for your heaviest jobs—but not as good for tasks like collaborative writing. - It's expensive. It's about twice as expensive as Opus, and it's also incredibly token hungry—so expect it to be something you'll use sparingly unless your company pays for it. Overall, I think of it like a warp drive for coding: It can get you across the galaxy in a few hours, when it used to take months or years. But it's not appropriate for getting around town—you need something faster, cheaper, and more maneuverable. The ceiling is extraordinarily high on this model though. Even our most advanced testers like Kieran Klaassen felt like they were only scratching the surface of it. Want our full vibe check with all of our testing and benchmarks? Read it on Every 📧:

Dan Shipper 📧

618,722 views • 1 month ago

I got to try Grok 4.5 in early access in Cursor for the past few days and I absolutely enjoyed it. It feels like Opus 4.8 at 2x the speed at a much cheaper price point. I tasked it to brainstorm > plan > implement a big feature for my game (this act 1 boss fight) and it did not disappoint. - It is much smarter than Composer 2.5, during planning mode, it is able to think through my request more robustly, ensuring that edge cases are covered and makes sure to ask the right questions to confirm with me first. - It is much better at brainstorming ideas/suggestions, similar to Opus 4.8, though I think Fable still edges out a little when it comes to brainstorming ideas and suggestions - It is FAST. probably the fastest of all frontier models (Opus 4.8, GPT 5.5 etc), which makes it a joy to build with, because I can stay in the flow - It has much improved visual/animation capabilities than Composer 2.5, it can code up animations (i wanted an explosion animation with particle effects) with much, much better visuals, animation movement and timing. This is a big leap and I was so happy to see this improvement. - The best part for me is that I can just use the same model from planning down to execution without switching to a lower cost model because the price point is cheaper than other frontier models. I'll be testing this model with more challenging tasks in the next few days but I think this is going to be my main driver for vibe coding for a while. Also, its nice to see Grok back in the race. 🙌

Danny Limanseta

1,311,553 views • 2 days ago

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 views • 11 months ago

Three months ago, Codex was trash for knowledge work. Now it's my daily driver. I use it for writing, recruiting, deep engineering work, and everything in between. It even keeps me at inbox 0. I chatted with Every 📧's head of growth Austin Austin Tedesco on Every 📧's AI & I about what changed, and why he now spends 80% of his working time in the Codex desktop app too. We get into: - How Codex went from making Austin feel like an idiot to being the place he goes to get stuff done, including complex tasks like writing go-to-market plans using existing material from Slack, Notion, and meeting transcripts. - Why the Codex’s desktop app, which is faster and more reliable than Claude Desktop/Cowork, is the real differentiator. - How I source candidates with Codex by having it identify career arcs, not keywords—my go-to move is identifying organizations likely to teach the skills Every needs for a role, and then find candidates from that pool who have since gone on to work in AI. This is a must-watch for anyone who's wondering whether it’s finally time to give Codex a try. Watch below! Timestamps How Codex went from a tool for senior engineers to a daily driver for knowledge work: 00:00:57 How Claude Code proved that a great coding agent works for any knowledge work: 00:02:42 Austin's switch to Codex: 00:07:24 How Austin set up Codex with folders, keys, and reviewer agents: 00:13:48 Using Codex to brainstorm automations across Gmail, Slack, and Notion: 00:18:24 How Austin manages the human review step when Codex is drafting communications: 00:22:42 Using Codex to build specialized agents inspired by product executive Claire Vo: 00:28:54 Synthesizing meeting transcripts and Slack threads into a go-to-market plan: 00:31:09 Building a live KPI tracker in Notion that agents can read: 00:40:15 Using Codex for recruiting: 00:44:54

Dan Shipper 📧

55,221 views • 2 months ago

GPT 5.6 Sol just saved me €650 a year and demonstrated just how good this model is as an agent in ChatGPT Codex. This is not a clickbait, let me explain. In France, insurance companies tend to hide all their prices behind quote forms that take at least 5min to complete for a single configuration on a single provider's website. And that take an other 5min to understand. If you want to compare 10 companies across 5 configurations each, it takes at least 4h +. (It's such a painful process that entire businesses exist just to compare insurance offers.) Since I have two cars, it would normally take me 8h so an entire day to have a real large view of my best option. Companies know this and use the friction to maintain overpriced offers. So I asked ChatGPT with GPT 5.6 Sol, using Chrome tabs, to go through all those annoying forms. I provided him all my contrats with my current insurance companies so he have context. For some insurers, you even have to speak with a representative just to get a quote (which is absurd in 2026), so it emailed the companies, exchanged the required information, and obtained the prices. It then ran a complete benchmark, read all the terms and conditions, and recommended three options from three different companies. I picked one, and it completed the subscription with my new insurance company. And that's how I ended up with better insurance coverage for less money. For 4% of my weekly quota in 20x plan. (i think it's fair) All of that happened while I was walking my dog for 50 minutes, he was working on my computer all by it's on. Yes, computer use existed before OpenAI GPT 5.6 Sol, but this is a completely different level in the way it handles these kinds of tasks. I think this story shows the new era of AI we're entering, good model is not only for one single task as coding or answering question, AI now can do things for you, like in your daily live. I love being able to hand my computer over to GPT 5.6 Sol. PS: The only annoying part was that some companies still require "Verify you're human" checks. In the age of AI agents, websites really need to be ready for robot access.

Defend Intelligence (Anis Ayari)

75,493 views • 2 days ago

The same kinds of productivity gains we've seen in coding with AI agents are heading to the rest of knowledge work. This is the jump when you go from having a chatbot to being able to actually have an agent go off and do work for minutes or even hours and come back with a complete work output that you then review. Here's an example of the new Box Agent filling out an RFP response from an existing knowledge base. This process would normally take hours to fill out, and requires the full attention of the user doing the work. Now, you provide the Box Agent with the RFP questions, and it will go off, make a plan, extract all the relevant questions, read through existing source material to come up with an answer, and then generate a new word document as the final output. All while you're doing something else. The key to this architecture is that the agent is able to use all of the same tools in the background that a user uses to get work done. The agent can search for documents, read entire files, run scripts and tools in the background, and even be able to write code on the fly to automate tasks it hasn't seen before. And best of all, the Box Agent will (soon) work from the Box MCP and CLI so you can invoke it in any agentic system as a step in a process. This kind of agent complexity would have been impossible even 6 months ago. Models consistently failed at tracking long running tasks or using the right tools at the right moment for the task. But this is all now possible because of models like GPT-5.4, Opus 4.6, and Gemini 3, and is only getting better by the month. Just as we moved from engineers writing code and using AI as an assistant to answer questions, in many areas of knowledge work -like legal, finance, consulting, sales, marketing, and more- when we have a problem we'll just kick off the AI agent to just go work on it for us in the background.

Aaron Levie

24,618 views • 3 months ago