Video of the Day14:13Mark Kashef · Tutorial
Don't Use Claude Fable 5 Until You See This
A 14-minute cost-routing playbook for the most powerful and expensive model Anthropic has ever shipped.
June 11thThe argument in one line.
The decisive advantage in AI tools is no longer the model itself but the wrapper around it — the memory, context, and workflow layer — and Karpathy joining Anthropic is a bet that wrapper quality is what wins.
Read if. Skip if.
READ IF YOU ARE…
- You use Claude Code daily and want to understand the product direction, not just the latest features.
- You follow AI industry moves and want a grounded read on why a specific hire matters beyond the headline.
- You are building with AI agents and want to understand what the shift from prompts to context engineering means practically.
SKIP IF…
- You want a technical deep dive into Karpathy's actual research — this is strategic commentary.
- You have no interest in Claude Code specifically — predictions are heavily Claude-ecosystem focused.
The full version, fast.
Most people read Karpathy joining Anthropic as a talent win. The deeper read: his entire public philosophy — context engineering, living knowledge bases, autonomous goal loops — maps almost exactly onto what Claude Code has been shipping. The model is becoming the smallest part of the AI experience; the wrapper (memory, skills, sub-agents, project docs) is where results and lock-in accumulate. Three predictions: a context marketplace, specialized /goal-style commands per domain, and an education layer that lets non-technical experts package knowledge into reusable Claude workflows.
Free for members
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.
00:00 – 01:05
01 · Cold open and promise
Karpathy joins Anthropic on May 19. Three things this video breaks down: why Karpathy specifically, what Anthropic is building underneath the model, and three predictions for Claude Code.
01:05 – 02:10
02 · Who is Karpathy?
Founding OpenAI member (2015), ran Tesla AI for 5 years (autopilot), returned to OpenAI 2023, left to start Eureka Labs (AI education), coined vibe coding.
02:10 – 04:00
03 · The Wrapper Thesis
The model is the smallest part of the experience. The real product is the wrapper — Claude Code, memory, project docs, skills, MCP connections. Context engineering replaces prompt engineering. Claude Code is an OS for the model.
04:00 – 05:57
04 · Why the timing matters
Ramp AI Index: Anthropic passed OpenAI in business adoption (34.4% vs 32.3%). Anthropic announced enterprise services JV with Blackstone, Hellman and Friedman, and Goldman Sachs.
05:57 – 08:40
05 · The roadmap hiding in plain sight
Karpathy's public projects read like a Claude Code roadmap: LLM Wiki (living markdown knowledge base), Auto Research (autonomous experiment loops), converging with /goal commands already shipping.
08:40 – 12:02
06 · Three predictions
Prediction 1: Anthropic builds a context app store. Prediction 2: Specialized /goal-style commands per domain. Prediction 3: Education layer for packaging expert knowledge into reusable Claude workflows.
Lines worth screenshotting.
- The same model produces excellent output for one user and garbage for another — the difference is the wrapper, not the model.
- Claude Code is not a coding tool. It is an operating system for the model.
- Context engineering is the skill that replaced prompt engineering — building the right environment, not writing the perfect prompt.
- Karpathy's LLM Wiki lets an agent build a living, relationship-aware knowledge base from raw markdown — no vector search needed.
- For solo operators, the data moat is meeting notes, SOPs, customer call transcripts, and internal naming conventions — not a massive database.
- The longer you build inside one AI operating system, the more painful switching becomes — the context cost is enormous.
- Anthropic passed OpenAI in business adoption at 34.4% vs 32.3% on the Ramp AI Index — a momentum signal, not a win declaration.
- Karpathy's Auto Research project is the same loop as /goal — propose a change, run the experiment, check metrics, iterate until done.
- Anthropic is building the model, the product surface, the partner network, and now a services layer — a different game from shipping a chatbot.
- A context marketplace is not a prompt library — it is subscribable domain-specific skills, workflows, memory schemas, and evaluation loops.
- The knowledge trapped in experts' heads and messy Notion docs is genuinely valuable — the missing piece is tooling to package it into reusable AI workflows.
- Evaluating AI tools by benchmark leaderboards is paying attention to the wrong layer entirely.
The model is not what you should be investing in.
WHAT TO LEARN
Benchmark rankings and model comparisons are a distraction — the compounding advantage is in the persistent context layer you build around whichever model you use.
- Two people with the identical model get radically different results because output quality comes from the environment built around the model, not the model itself.
- Context engineering — building persistent memory, project docs, examples, and workflow structure — is the successor skill to prompt engineering.
- The longer you invest in a well-structured AI setup, the higher the switching cost becomes — not because you are locked in, but because your accumulated context is genuinely valuable.
- For individuals and small teams, the data moat is meeting notes, SOPs, customer call transcripts, and institutional knowledge currently trapped in documents nobody reads.
- Autonomous goal-setting loops (set a target, let the agent iterate until complete) represent a qualitative shift in how AI tools feel — closer to delegating to a person than querying a search engine.
- A context marketplace — subscribable domain-specific workflows, evaluation loops, and knowledge schemas — is the missing layer between raw model capability and practical daily usefulness.
- Watching model benchmark leaderboards as a proxy for AI tool quality is the equivalent of judging a car by its engine specs without driving it.
Terms worth knowing.
- Context engineering
- Designing the full environment a model operates in — memory, examples, schemas, project docs — rather than crafting individual prompts. Coined by Karpathy as the successor skill to prompt engineering.
- Wrapper
- The full system surrounding an AI model: interface, memory layer, sub-agents, hooks, project configuration, and tooling. The wrapper, not the model, determines real-world output quality.
- LLM Wiki
- A Karpathy-designed system where an AI agent reads a folder of markdown files and builds a structured, relationship-aware knowledge base — understanding how documents connect rather than doing flat keyword search.
- Auto Research
- Karpathy's autonomous experiment loop: the agent proposes a change, runs a short experiment, checks results against objective metrics, and keeps iterating until it hits the target.
- Ramp AI Index
- A dataset from corporate card company Ramp tracking real business spending on AI models and platforms across their customer base, used as a proxy for enterprise AI adoption trends.
- Vibe coding
- Term coined by Karpathy for describing what you want in plain English and letting the AI write the code while you steer, iterate, and ship.
Things they pointed at.
04:24linkAnthropic / Blackstone enterprise JV
07:43linkKarpathy Auto Research
01:18linkEureka Labs
Lines you could clip.
02:50
“The real product isn't the model. The real product is the wrapper around the model.”
03:44
“Claude Code isn't really a coding tool. It's an operating system for the model.”
08:26
“It stops feeling like a chatbot, and it starts feeling like an employee who actually finishes things.”
11:23
“If you're still staring at benchmarks, you are paying attention to the wrong layer.”
Word for word.
Read-along
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
metaphoranalogy
Okay. So a few days ago, May 19, to be specific, Andre Karpathy posted a tweet that I think most people just scrolled by. He announced he's joining Anthropic.
And on the surface, this is one of those headlines where you go, yeah. Okay. A huge computer scientist joins a frontier lab.
What's the big deal? What's for dinner? But the more I sit with this one, the more I realize this isn't just a hire.
It's a signal. And if you use Claude code or you're paying any attention at all to where AI is heading over the next six to twelve months, this move tells you almost everything you need to know about what's coming. So in this video, I wanna break down three things.
First, why Carpathi specifically? Because every big lab on the planet has been trying to land this guy for years. Second, what Anthropic is actually building underneath the model?
Because I think most people are still staring at the wrong layer of this whole thing. And third, I wanna give you three predictions for what QuadCode is going to ship next based on patterns Karpathy has been quietly dropping in public for months. Let's get into it.
Real quick, for anyone who doesn't know who Karpathy is, he is genuinely one of the most influential people in modern AI, full stop. He's a founding member of OpenAI back in 2015.
He ran AI at Tesla for about five years, and that's where a huge chunk of the autopilot stack got built. Then he went back to OpenAI in 2023, left a year later, started Eureka Labs, which was basically his AI education company.
He's also the guy who coined the term vibe coding, which, let's be honest, is one of the most used terms and what we're actually all doing right now, whether we admit it or not.
You describe what you want in plain English, and AI writes it. You steer, you iterate, you ship. So when somebody at that level moves, we have to pay attention.
But the question that hit me when I saw the tweet wasn't did he join Anthropic, it was why Anthropic and why now?
Because OpenAI, Google, Meta, x AI, every single one of them would have rolled the red carpet out for this guy. So why this lab?
Here's where it gets interesting. Most people still talk about AI like the model is everything. Right?
Is GPT 5.5 better than OPUS four point whatever? What's number one on the leaderboard this week? Which benchmark is the new benchmark?
And look, the model does matter. I'm not pretending that it doesn't, but I'll tell you what I've noticed after living in these tools every single day for the last however many months. The model is becoming the smallest part of the actual experience.
You can hand two people the same exact model, one person ships god tier output, the other person gets garbage.
It's the same model, but you get wildly different results. Why? Because the real product isn't the model.
The real product is the wrapper around the model. And when I say wrapper, I mean the whole environment the model lives inside of. Claude code is a wrapper.
Codex is a wrapper. Skills sub agents, hooks, MCP connections, your claw dot MD file, your memory, your project docs, your examples of what good looks like, all of that is a wrapper.
This is exactly what Carpathi has been preaching for over a year. He's the one guy who coined the phrase context engineering instead of prompt engineering.
His whole point is the skill isn't writing the perfect prompt anymore. The skill is building the right environment around the model so it can actually do useful work over and over again and remember what it learned last time. And here's the part that clicked for me.
Anthropic has been quietly building exactly that. Cloud Code isn't really a coding tool. It's .
In Carpathi's entire public philosophy and what Anthropic has been shipping for the last year, .
That is not a coincidence. Now let me show you why this timing is so wild. About a week ago, Ramp dropped their AI index.
Ramp tracks business spending across their customer base so that this is real money, real companies, real adoption. And for the first time in their data, Anthropic passed OpenAI in business adoption, 34.4% to 32.3%.
Now I wanna be careful here. This is Ram's customers. It's not the entire market.
OpenAI still has a bigger consumer brand and massive enterprise deals that probably don't even show up in this data. So I'm not saying Anthropic has won, but it is a momentum signal you cannot ignore.
And earlier this month, this is the part I think people are sleeping on, Anthropic announced they're launching an enterprise AI services company, like a joint venture with Blackstone, Hellman and Friedman, and Goldman Sachs. The whole point is helping mid sized businesses actually deploy Claude into the real operations.
Now stop and think about what that actually means. Anthropic isn't just saying, here's the model. Good luck.
They're building the model, the product surface, and the partner network, and now a services layer that walks companies through adoption.
That is a completely different game from shipping a chatbot, and it all points to the same thesis. The model is not the moat forever. The moat is the application layer.
It's how Quad gets embedded into the workflows where companies actually make money, save time, and scale without hiring. So when you zoom out, Anthropic is racing to own the rapper.
Carpathi has been the loudest voice on the planet about why the rapper is the most important part. And of course, he joined Anthropic. The only surprise is that it didn't happen sooner.
Okay. This is where it gets really fun. Because if you actually go back and look at Karpathy's public work over the last six months, it reads like a road map for where Claude code is heading.
Back in April, he released this thing he called the LLM Wiki. But the short version is you can create a raw folder full of markdown files. You give the agent a schema document explaining how the system works.
The agent synthesizes everything, builds connections between files, maintains a living, evolving knowledge base that you can read, understand, and add to over time.
So instead of the model doing some dumb vector search across all of your stuff, it actually understands the relationships between your documents. People started building their entire second brains with this thing.
It went viral for a reason. And here's what matters for you specifically. When people say data is the moat, most folks picture some massive enterprise database.
But for normal builders, for small businesses, for solo operators, . It's your meeting notes.
It's your internal SOPs, your customer call transcripts, your weird internal naming conventions.
It's the stuff that makes the business actually yours. If Claude can turn that into usable context that the model actually sees and uses every time you open a chat, the model gets smarter and more useful to you specifically every single week. That is the lock in.
Not because you can't switch models, you absolutely can, but because the longer you live inside this operating system and the more context and memory the workflows have of your information, the more painful it gets to leave. Then in March, Karpathy dropped a project called Auto Research.
The idea is to set up an autonomous loop. It takes a script, proposes changes, runs a short experiment, checks the results against objective metrics, and just keeps iterating until it hits the target.
And then very recently, Codex shipped slash goal. Hermes scored a slash goal. ClaudeCode shipped its own native slash goal.
Same exact pattern. You define the outcome. The agent works until it gets there.
When you come back, it's done. Now look. I'm not claiming Carpathi personally invented this.
I have no idea who shipped what first, but the pattern is clearly the same. We are moving away from one prompt, one answer, and toward set the goal and let it run.
And this is the massive shift you need to know how to interact with when using these tools. It stops feeling like a chatbot, and it starts feeling like an employee who actually finishes things. Alright.
Let me give you three predictions. And just to be clear, this is me reading the tea leaves. I don't have insider information.
I'm not on Anthropix road map calls. But if you connect the dots between what Carpathi has built in public and what Claude Code has already shipped, the direction is honestly not that subtle. Prediction one, Anthropic is going to build an app store for context.
And I don't mean a prompt marketplace. Everyone is tired of that. I mean something deeper.
Skills, workflows, project memories, domain specific contexts, evaluation loops, connectors to real data, examples that teach the model what good looks like inside of a specific job.
Imagine being able to subscribe to world class real estate intake workflow or FP and A monthly close template and bolt it straight onto your Claude code setup.
That's where this is going. Prediction two. We're going to see a lot more slash goal style commands, but specialized.
Right now, slash goal is pretty general, but I think we're going to see slash research slash debug slash audit slash launch commands that aren't just keep going until you're done, but keep going until you're done in this specific vertical with these specific success criteria. Same pattern, more specialized harnesses around it, and now prediction three.
And this is the one that I'm least sure about, but the one that I find most interesting. Anthropic shifts an education layer for packaging your own workflows. So hear me out.
Carpathi's entire last company was an education play. His superpower is taking insanely technical concepts and making them feel approachable.
And if Anthropic actually wants a real context marketplace, they don't just need developers contributing. They need normal subject matter experts.
The accountant who knows the monthly close code. The real estate agent who knows every step of a property intake. The YouTuber who knows good packaging from bad packaging.
The knowledge is genuinely valuable. But right now, it's all trapped in people's heads or buried in messy notion docs and Slack threads nobody reads. If Anthropic builds a layer that helps nontechnical experts actually package their knowledge into reusable cloud workflows, that is a marketplace nobody else has ever tried to build yet.
So look at the headline here. Karpathy joined Anthropic. The headline is the most influential person in AI education and context engineering just joined the company that's been quietly building the best rapper in the industry.
And if you're still staring at benchmarks, you are paying attention to the wrong layer. If this kind of breakdown is useful to you, do me a favor and hit the like button. It genuinely helps the channel a ton.
And drop a comment with which of those three predictions you think ships first because I want to see if I'm crazy or if you see it too. And if you wanna go deeper into all this, I made a full walkthrough of the building your own LLM Wiki inside of Claude Code this weekend.
No waiting for Anthropic to ship anything. It is the closest thing to running your own personal AI operating system right now, and it's right there on the screen. Go check it out.
I'll see you in the next one.
The Hook
The bait, then the rug-pull.
On May 19, one of the most influential people in modern AI posted a tweet most people scrolled past. Read carefully, it tells you almost everything about where Claude Code is heading over the next twelve months — and why the model benchmarks you have been watching are the wrong thing to measure.
Named ideas worth stealing.
02:10concept
The Wrapper Thesis
The model is the smallest part of AI tool value. The full environment wrapped around it — memory, context, examples, sub-agents — is where output quality is determined and where lock-in accumulates.
Steal forframing why investing in Claude Code setup pays off more than chasing the latest model
03:15concept
Context Engineering
Coined by Karpathy. The skill shifted from writing the perfect prompt to building the right persistent environment so the model can do useful work repeatedly and remember what it learned.
Steal forexplaining why CLAUDE.md files, project memory, and skill systems matter more than model selection
06:17model
LLM Wiki pattern
- Raw markdown folder
- Schema document
- Agent synthesis pass
- Relationship graph
- Living knowledge base
A raw folder of markdown files plus a schema document. An agent synthesizes everything, builds connections between files, and maintains a living knowledge base with relationship awareness rather than flat vector search.
Steal forbuilding persistent project memory inside Claude Code that compounds over time
How they asked for the click.
VERBAL ASK
11:23next-video
“I made a full walkthrough of building your own LLM Wiki inside of Claude Code this weekend. No waiting for Anthropic to ship anything.”
Soft confident close. Like + comment prompt first, then video recommendation with end screen.
MENTIONED ON CAMERA
FROM THE DESCRIPTION
PRIMARY CTAWhere the creator wants you to go next.
OTHER LINKSAlso linked in the description.
Visual structure at a glance.
