Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

CLAUDE CODE + SELF-CORRECTING LOOP = THE FASTEST WAY TO BUILD AND MONETIZE APPS most developers burn thousands of dollars manually debugging this setup forces Claude Opus 4.8 to self-correct - replacing a $95k/year QA engineer with a loop that costs $20/month: > Builder agent writes code while Checker... show more

Mr. Buzzoni

20,234 subscribers

35,357 views • 11 days ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Anthropic engineer: "Over 90% of Anthropic engineers use a self-improving agentic loop for coding. The key is to close the loop: give the agent a way to verify and improve its own work" In this 12-minute talk, an Anthropic engineer explains how to build an agent that continuously improves itself. Claude + routines + loops + CLAUDE.md - that's the foundation. Skip Netflix tonight. Save this post!

Anthropic engineer: "Over 90% of Anthropic engineers use a self-improving agentic loop for coding. The key is to close the loop: give the agent a way to verify and improve its own work" In this 12-minute talk, an Anthropic engineer explains how to build an agent that continuously improves itself. Claude + routines + loops + CLAUDE.md - that's the foundation. Skip Netflix tonight. Save this post!

unicode

61,445 views • 9 days ago

THIS 11-PAGE CLAUDE LOOP ENGINEERING PLAYBOOK IS THE CHEAT CODE FOR SENIOR DEV PROMOTIONS typing prompts line by line won't get you hired. you need to know how to design self-prompting loops: > Discovery: agent finds its own work from logs, failing tests, and commits > Handoff: tasks execute in isolated git worktrees to prevent parallel collisions > Verification: a second reviewer agent audits the builder's code to catch blind spots > Persistence and Scheduling: code writes to disk and loops run 24/7 on a timer the shift is simple: stop prompting the agent, build the system that prompts it read the full setup blueprint 👇

THIS 11-PAGE CLAUDE LOOP ENGINEERING PLAYBOOK IS THE CHEAT CODE FOR SENIOR DEV PROMOTIONS typing prompts line by line won't get you hired. you need to know how to design self-prompting loops: > Discovery: agent finds its own work from logs, failing tests, and commits > Handoff: tasks execute in isolated git worktrees to prevent parallel collisions > Verification: a second reviewer agent audits the builder's code to catch blind spots > Persistence and Scheduling: code writes to disk and loops run 24/7 on a timer the shift is simple: stop prompting the agent, build the system that prompts it read the full setup blueprint 👇

Mr. Buzzoni

44,111 views • 11 days ago

Boris Cherny runs Claude Code at Anthropic. His line should stop you mid-scroll: "I don't prompt Claude anymore. I have loops running that prompt Claude and figure out what to do. My job is to write loops." The skill moved. From writing prompts to building the loop around them. A loop that works has three things. Drop one and it burns money in circles. 1. A finish line it can prove. Tests pass or they fail. "Looks done" is not a finish line. 2. A checker that did not write the code. A model grading itself always says yes. 3. Brakes set before you start. A step limit. A money ceiling. A stop condition. That is the whole game. The loop does the work. You design the cage it runs in. Full breakdown below.

Boris Cherny runs Claude Code at Anthropic. His line should stop you mid-scroll: "I don't prompt Claude anymore. I have loops running that prompt Claude and figure out what to do. My job is to write loops." The skill moved. From writing prompts to building the loop around them. A loop that works has three things. Drop one and it burns money in circles. 1. A finish line it can prove. Tests pass or they fail. "Looks done" is not a finish line. 2. A checker that did not write the code. A model grading itself always says yes. 3. Brakes set before you start. A step limit. A money ceiling. A stop condition. That is the whole game. The loop does the work. You design the cage it runs in. Full breakdown below.

shmidt

16,085 views • 14 days ago

Boris Cherny: "My job is to write loops." 5-day version you can copy for Claude Code Day 1: repo memory - write CLAUDE.md - include stack, test commands, code style, release rules, gotchas - add .claude/settings.json with the shell commands Claude can run Day 2: verification skill - pick 1 flow Claude keeps breaking - put the browser/API test in .claude/skills/ /scripts/ - make it return: pass/fail, failing step, screenshot/log path Day 3: commands Add these files: .claude/commands/babysit.md - checks your PRs - reads CI - handles obvious review nits - surfaces design questions .claude/commands/triage-issues.md - labels new issues - dedupes against existing ones - assigns owners .claude/commands/deploy-watch.md - checks the live app - reports regressions - avoids touching production Day 4: loops > /loop 5m /babysit > /loop 15m /triage-issues > /loop 5m /deploy-watch Day 5: overnight work - schedule /morning-report - schedule /deep-audit - write results to .claude/inbox/ - let your morning loop read from that folder The rule: every code-writing loop gets a separate verifier. Builder makes the change. Verifier runs the real app. You read the diff. Skip that and you wake up to 14 broken PRs with very confident summaries. Video: "Reflecting on a year of Claude Code" with Boris Cherny & Cat Wu

Boris Cherny: "My job is to write loops." 5-day version you can copy for Claude Code Day 1: repo memory - write CLAUDE.md - include stack, test commands, code style, release rules, gotchas - add .claude/settings.json with the shell commands Claude can run Day 2: verification skill - pick 1 flow Claude keeps breaking - put the browser/API test in .claude/skills/ /scripts/ - make it return: pass/fail, failing step, screenshot/log path Day 3: commands Add these files: .claude/commands/babysit.md - checks your PRs - reads CI - handles obvious review nits - surfaces design questions .claude/commands/triage-issues.md - labels new issues - dedupes against existing ones - assigns owners .claude/commands/deploy-watch.md - checks the live app - reports regressions - avoids touching production Day 4: loops > /loop 5m /babysit > /loop 15m /triage-issues > /loop 5m /deploy-watch Day 5: overnight work - schedule /morning-report - schedule /deep-audit - write results to .claude/inbox/ - let your morning loop read from that folder The rule: every code-writing loop gets a separate verifier. Builder makes the change. Verifier runs the real app. You read the diff. Skip that and you wake up to 14 broken PRs with very confident summaries. Video: "Reflecting on a year of Claude Code" with Boris Cherny & Cat Wu

Alpha Batcher

141,110 views • 26 days ago

Anthropic Research Lead: "99% of our engineers run swarms of 300+ self-improving agents" "Close the loop, give the model a way to verify its own output" In a 20-minute session, an Anthropic Team member breaks down how to build agents that improve themselves The real setup is Claude running through loops, plan mode, and dynamic workflows Better than most $300 agent courses Bookmark and watch the talk Then read the article below

Anthropic Research Lead: "99% of our engineers run swarms of 300+ self-improving agents" "Close the loop, give the model a way to verify its own output" In a 20-minute session, an Anthropic Team member breaks down how to build agents that improve themselves The real setup is Claude running through loops, plan mode, and dynamic workflows Better than most $300 agent courses Bookmark and watch the talk Then read the article below

rari

377,971 views • 13 days ago

i'm a little sick of chatgpt giving me obviously broken code i've found a "micro agent" approach to LLM code generation can work much better the LLM first generates a *test*, and then enters a loop where it generates and iterates on the code until the tests pass source below

i'm a little sick of chatgpt giving me obviously broken code i've found a "micro agent" approach to LLM code generation can work much better the LLM first generates a test, and then enters a loop where it generates and iterates on the code until the tests pass source below

Steve (Builder.io)

544,171 views • 2 years ago

OpenAI engineer: “90% of our engineers use Codex subagent harnesses + loops to ship code 5× faster. close the agent loop. Give an agent a way to verify its own output.” in 30-minute talk, an OpenAI engineer explains how to build self-improving agentic systems with harnesses. Worth more than a $500 agentic course online. Watch it today, then read how hedge funds apply loop engineering in trading.

OpenAI engineer: “90% of our engineers use Codex subagent harnesses + loops to ship code 5× faster. close the agent loop. Give an agent a way to verify its own output.” in 30-minute talk, an OpenAI engineer explains how to build self-improving agentic systems with harnesses. Worth more than a $500 agentic course online. Watch it today, then read how hedge funds apply loop engineering in trading.

Movez

39,438 views • 12 days ago

Spotify Chief Architect, Niklas Gustavsson: "Once we added loops, our agent success rate went from 20-30% to 80%." Everyone's chasing a smarter model. Spotify just built a better loop. 26 min with Claude Code creator Boris Cherny on how they run agents across a 20M-line monorepo. 73% of PRs are AI-assisted. 4,500 deploys a day. 2,900 engineers. loops + a verifier that runs CI + a house-style codebase + auto-merge - that's the secret. close the loop: let the agent run the build, read what failed, and fix itself. Watch the talk, then save the playbook.

Spotify Chief Architect, Niklas Gustavsson: "Once we added loops, our agent success rate went from 20-30% to 80%." Everyone's chasing a smarter model. Spotify just built a better loop. 26 min with Claude Code creator Boris Cherny on how they run agents across a 20M-line monorepo. 73% of PRs are AI-assisted. 4,500 deploys a day. 2,900 engineers. loops + a verifier that runs CI + a house-style codebase + auto-merge - that's the secret. close the loop: let the agent run the build, read what failed, and fix itself. Watch the talk, then save the playbook.

shmidt

21,748 views • 5 days ago

Boris Cherny (Claude Code creator): "I don't prompt Claude anymore... my job is to write loops." In his latest interview, he breaks down the setup step by step. He runs /loops + a dynamic workflow + a couple hundred agents that read his GitHub, Slack, and Twitter and decide what to build next. His only job now is writing the loops that orchestrate them. That's a multi-agent workflow. I broke down how to build your own below ↓

Boris Cherny (Claude Code creator): "I don't prompt Claude anymore... my job is to write loops." In his latest interview, he breaks down the setup step by step. He runs /loops + a dynamic workflow + a couple hundred agents that read his GitHub, Slack, and Twitter and decide what to build next. His only job now is writing the loops that orchestrate them. That's a multi-agent workflow. I broke down how to build your own below ↓

Avid

26,751 views • 29 days ago

Spotify Chief Architect, Niklas Gustavsson: "Once we implemented loops in our workflow, our agent success rate went from 20-30% to 80%." 26 minutes with Claude Code creator Boris Cherny on how Spotify runs AI agents across 20 million lines of code. Today 73% of their code is written by AI, most merged without a human ever seeing it. The model matters less than the loop you build around it. Watch it, then read the full guide on building loops below.

Spotify Chief Architect, Niklas Gustavsson: "Once we implemented loops in our workflow, our agent success rate went from 20-30% to 80%." 26 minutes with Claude Code creator Boris Cherny on how Spotify runs AI agents across 20 million lines of code. Today 73% of their code is written by AI, most merged without a human ever seeing it. The model matters less than the loop you build around it. Watch it, then read the full guide on building loops below.

Anatoli Kopadze

830,752 views • 6 days ago

an OpenAI engineer just showed how he gets agents to do his whole job: code, debug and more, using loops 29 minutes from the engineer who coined "harness engineering" he writes the rules, agents write the code, a reviewer agent loops until it's right the winners won't have the smartest model, they'll have the best loop around it watch it, then read the full guide on loops below

an OpenAI engineer just showed how he gets agents to do his whole job: code, debug and more, using loops 29 minutes from the engineer who coined "harness engineering" he writes the rules, agents write the code, a reviewer agent loops until it's right the winners won't have the smartest model, they'll have the best loop around it watch it, then read the full guide on loops below

Anatoli Kopadze

172,960 views • 13 days ago

ANTHROPIC LEAD ENGINEER MAKING $2.3M/YEAR JUST LEAKED A 12-PAGE DOCUMENT - AND GOT FIRED 15 MINUTES AFTER PUBLISHING most developers build loops - but almost every loop breaks in one of five ways, and each failure has a symptom visible from the outside without reading a single line of code > Blind loop - the agent waits for a human to hand it work every morning - automating execution but not discovery > Tangled loop - parallel agents share one directory and overwrite each other parallelism that destroys instead of multiplies > Nodding loop - the agent grades its own work and approves it every time a loop that has never said no to itself is broken > Amnesiac loop - results live only in the context window every morning the system wakes up with no memory of yesterday > Manual loop - no trigger a human presses the button to start it that is not a loop that is a script waiting for a person a real loop finds its own work - remembers what it did has something that can say no never lets two agents touch the same file and fires itself on a timer remove any one of the five - and the loop either breaks or never starts 12 pages that changed how I build agentic systems today

ANTHROPIC LEAD ENGINEER MAKING $2.3M/YEAR JUST LEAKED A 12-PAGE DOCUMENT - AND GOT FIRED 15 MINUTES AFTER PUBLISHING most developers build loops - but almost every loop breaks in one of five ways, and each failure has a symptom visible from the outside without reading a single line of code > Blind loop - the agent waits for a human to hand it work every morning - automating execution but not discovery > Tangled loop - parallel agents share one directory and overwrite each other parallelism that destroys instead of multiplies > Nodding loop - the agent grades its own work and approves it every time a loop that has never said no to itself is broken > Amnesiac loop - results live only in the context window every morning the system wakes up with no memory of yesterday > Manual loop - no trigger a human presses the button to start it that is not a loop that is a script waiting for a person a real loop finds its own work - remembers what it did has something that can say no never lets two agents touch the same file and fires itself on a timer remove any one of the five - and the loop either breaks or never starts 12 pages that changed how I build agentic systems today

Sprytix

111,225 views • 1 day ago

Built a Skool clone with Claude Code (Opus 4.5), with auth, db + storage with the new web app builder. (Launching next week). We are building the easiest way to use the most powerful coding model (Claude Code) in the world to build mobile apps and web apps. No performative hour long agent runs that waste tokens. Just raw Claude Code running in a sandbox, pre built with skills that make frontend + backend just work. Let me know if you want to beta test.

Built a Skool clone with Claude Code (Opus 4.5), with auth, db + storage with the new web app builder. (Launching next week). We are building the easiest way to use the most powerful coding model (Claude Code) in the world to build mobile apps and web apps. No performative hour long agent runs that waste tokens. Just raw Claude Code running in a sandbox, pre built with skills that make frontend + backend just work. Let me know if you want to beta test.

Riley Brown

50,857 views • 6 months ago

Claude Code creator: "Loops are as big a step as move from source code to agents. Loops - step from agents to the next thing. 30% of my code is fully written by loops right now." in a 40-minute fireside chat, Boris Cherny reveals his actual working setup. Loops + dynamic workflows + routines, and more. Watch the full episode, then read the article on loop engineering below.

Claude Code creator: "Loops are as big a step as move from source code to agents. Loops - step from agents to the next thing. 30% of my code is fully written by loops right now." in a 40-minute fireside chat, Boris Cherny reveals his actual working setup. Loops + dynamic workflows + routines, and more. Watch the full episode, then read the article on loop engineering below.

Movez

374,102 views • 16 days ago

Anthropic engineers just showed how they build a full app from scratch, using a loop of agents 40 minutes from the team behind Claude Code they used three agents: one to plan, one to build, one to judge, cycling until the app actually works the winners won't have the smartest model, they'll have the best loop watch it, then read the full guide on how to actually use loops below

Anthropic engineers just showed how they build a full app from scratch, using a loop of agents 40 minutes from the team behind Claude Code they used three agents: one to plan, one to build, one to judge, cycling until the app actually works the winners won't have the smartest model, they'll have the best loop watch it, then read the full guide on how to actually use loops below

Anatoli Kopadze

1,889,526 views • 15 days ago

Old way of using Claude Code: Prompt → wait → review → prompt → wait → review → repeat 20 times. You are the loop. You are the condition check. You are the reason it keeps going. New way: /goal all tests pass and lint is clean Claude works. You do something else. You come back to a result. Here's exactly how to set it up — and how to write conditions that actually work ↓

Old way of using Claude Code: Prompt → wait → review → prompt → wait → review → repeat 20 times. You are the loop. You are the condition check. You are the reason it keeps going. New way: /goal all tests pass and lint is clean Claude works. You do something else. You come back to a result. Here's exactly how to set it up — and how to write conditions that actually work ↓

Rahul

37,933 views • 1 month ago

Anthropic research lead: "99% of our engineers are running swarms of 300+ self-improving agents. close the agent loop. Give the model a way to verify its own output" in a 20-minute session, Anthropic team member explains how to build a model that improves itself. Claude + loops + plan mode + dynamic workflows -that’s the secret. Watch the talk, then save the playbook below.

Anthropic research lead: "99% of our engineers are running swarms of 300+ self-improving agents. close the agent loop. Give the model a way to verify its own output" in a 20-minute session, Anthropic team member explains how to build a model that improves itself. Claude + loops + plan mode + dynamic workflows -that’s the secret. Watch the talk, then save the playbook below.

Codez

661,437 views • 18 days ago

Claude Code costs $200/month here's how to run it for free. 4 commands. 10 minutes step 1 - install Ollama runs AI models locally → download from → install. it runs in background on localhost:11434 step 2 - download a coding model → ollama pull qwen2.5-coder:14b (7b for 8GB RAM, 32b for 32GB+ RAM) step 3 - redirect Claude Code to your machine → export ANTHROPIC_BASE_URL= → export ANTHROPIC_MODEL=qwen2.5-coder:14b step 4 - launch → claude → "make a hello world website" → it reads files, writes code, runs commands. locally. free same agent loop. same tools. $0/month the $200 was for convenience the capability was always free like + bookmark - you'll need this

Claude Code costs $200/month here's how to run it for free. 4 commands. 10 minutes step 1 - install Ollama runs AI models locally → download from → install. it runs in background on localhost:11434 step 2 - download a coding model → ollama pull qwen2.5-coder:14b (7b for 8GB RAM, 32b for 32GB+ RAM) step 3 - redirect Claude Code to your machine → export ANTHROPIC_BASE_URL= → export ANTHROPIC_MODEL=qwen2.5-coder:14b step 4 - launch → claude → "make a hello world website" → it reads files, writes code, runs commands. locally. free same agent loop. same tools. $0/month the $200 was for convenience the capability was always free like + bookmark - you'll need this

self.dll

177,607 views • 2 months ago

1 HOUR WITH KARPATHY. SAVE THIS BEFORE YOU OPEN CLAUDE CODE TODAY > autonomous agents that improve themselves without a human in the loop that's where Claude Opus 4.8 is heading > the 32 skills in this article are the foundation Karpathy explains what's coming

1 HOUR WITH KARPATHY. SAVE THIS BEFORE YOU OPEN CLAUDE CODE TODAY > autonomous agents that improve themselves without a human in the loop that's where Claude Opus 4.8 is heading > the 32 skills in this article are the foundation Karpathy explains what's coming

Mr. Buzzoni

69,151 views • 1 month ago

Ex-Google engineer reveals how to build AI agent loops, harnesses, LLM ops, and evals in 19 minutes. Trace → evaluate → diagnose → fix → ship → repeat. That loop is how agents self-improve over time. Agentic loops + harness + memory + evals - that’s the senior engineer stack. This is better than $500 paid courses on the same topic, explained in under 20 minutes. Watch it, then save the framework below.

Ex-Google engineer reveals how to build AI agent loops, harnesses, LLM ops, and evals in 19 minutes. Trace → evaluate → diagnose → fix → ship → repeat. That loop is how agents self-improve over time. Agentic loops + harness + memory + evals - that’s the senior engineer stack. This is better than $500 paid courses on the same topic, explained in under 20 minutes. Watch it, then save the framework below.

Codez

160,510 views • 6 days ago