Lenny's AI Builders - LAB 0040 the boss and workers setup, one prompt to test two models blind, and the Fable reset catch. Claude Fable 5.2 just dropped and there's only one task i'd actually pay it for. the one task is the boss. it reads the task, picks which worker gets it and knows when it's actually good. Opus 5.5 already does the work. so i ran Fable 5.2 against Opus 5.5 on 10 kinds of my real work. even if it wins, i'm still not letting it do the work. why it mattersAI just got a pay scale. there's a boss rate and a worker rate, and i think most of us are paying the boss to do the worker's hours. Anthropic's own launch page says start with Opus 5.5 for most coding and knowledge work, and keep Fable for the most ambitious open-ended stuff. there are two cost stories and both are true. Anthropic says Fable on high matches Opus's best for roughly half the cost per task. Artificial Analysis measured Fable at about 2.6 times the cost per task at max effort. so the effort setting moves your bill. what you get
the real example: my runi ran Fable 5.2 against Opus 5.5 on BuilderBench, my own benchmark. 10 kinds of my real work, marked blind, so i didn't know which one did which. i made my bet before i saw a single score: Fable wins my bench, but barely. and i don't think it will matter much, because i'm not buying Fable to do the work. the result is in the video at 10:35. one catch: Fable hit a usage limit mid-run, so the scores carry an asterisk. the first thing i did with Fable was get it to plan this episode. it wrote me a take and i told it "that sounded like AI slop". AI can do a lot of this stuff, but i do write my own take. in T3 Code i run the workers as separate threads, not subagents. about 12 hours in, the workload already feels lighter. that's a feeling, not a measurement. try it
copy this promptpaste this into Claude or any AI, with your two answers under it:
my test in the episode ran on BuilderBench, my own tool. this prompt is the small version you can run today. i didn't run this exact prompt on camera. you'll know it worked whenyou picked A or B before you knew which model wrote it, and you can say why in one line. do that on a few kinds of work and you'll know which model gets which seat on your own tasks. a bad result: you already know which model wrote which answer. then it isn't blind. swap the labels and go again. limits and dates
the rest of this LAB
sources
next stepwatch LAB 0040 on YouTube - the bench starts at 10:35. want the next one? get the next field notes. optional - these notes stay free to read. |
i’m Lennox. i sift through AI Twitter and share one thing i tried with ChatGPT. for people making products, content and useful systems. five emails a week, with a weekly option.
Lenny's AI Builders - LAB 0045 one Claude Code setting, 36 to 38% fewer tokens in every pair of my test, the catch on cost, and a prompt that gives you 10 versions. if you build with Claude Code, one new setting can make it use fewer tokens. i tested this myself. every pair of runs used 36 to 38% fewer tokens. but there is a catch. my first run cost 83% more at api prices. the other two pairs came out 15% and 17% cheaper. why it matters the setting turns on Code Mode. Claude writes code that...
Lenny's AI Builders - LAB 0042 the one Grok Bot upgrade that matters, and the paragraph i add to claude.md for long Fable 5.2 jobs. Grok Bot 1.0 isn't new, but the launch post pulled 46 million views like it was. so don't worry, you're not missing out. the one upgrade that's actually decent got something like 40 times fewer views. and it let my bot walk into my Mac. why it matters Grok Bot has been out since August. xAI's own page calls 1.0 a major update to its AI teammates. the headline...
Lenny's AI Builders - LAB 0041 the conductor paragraph, the four steps to run it, and the honest numbers from my 40-hour run. i ran my viral Fable 5.2 conductor for 40 hours on my real app. one conductor, 73 worker threads, 25 pull requests merged. and my weekly Fable limit was gone in 13 hours. so here's what it actually built, and the one paragraph that runs yours. why it matters this is the new meta. you use Fable 5.2 as the conductor and Opus 5.5 as the worker threads. Fable 5.2 is twice...