Loading video...

Video Failed to Load

Go Home

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...

Sprytixl's profile picture

Sprytix

5,701 subscribers

153,575 views • 1 month ago •via X (Twitter)

EducationScience & Technology
LIVE

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!
12:06

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

62,153 views • 1 month ago

Creator of agent loops: "Anthropic also using my agent systems formula and still the biggest mistake in agents: is skipping Graphs" his 3 rules for every agent: rule 1 → loop it, don't run once - think, act, observe, repeat - cut the context and it forgets why it started rule 2 → an agent is memory + tools + reasoning - drop one and it breaks rule 3 → stop fine-tuning the model - the real alpha is the infrastructure around it the formula behind every AI agent - explained by the one who wrote it one agent → a loop → a graph of loops → a system that never forgets watch & bookmark - then read how to wire it into a graph ↓
45:37

Creator of agent loops: "Anthropic also using my agent systems formula and still the biggest mistake in agents: is skipping Graphs" his 3 rules for every agent: rule 1 → loop it, don't run once - think, act, observe, repeat - cut the context and it forgets why it started rule 2 → an agent is memory + tools + reasoning - drop one and it breaks rule 3 → stop fine-tuning the model - the real alpha is the infrastructure around it the formula behind every AI agent - explained by the one who wrote it one agent → a loop → a graph of loops → a system that never forgets watch & bookmark - then read how to wire it into a graph ↓

codila

23,915 views • 19 days ago

HOW TO USE AI LOOPS TO RUN YOUR BUSINESS 24/7 A lot has been written about loop engineering for building products. Almost nothing about using loops to run the business itself. That's the bigger idea. A loop is when you give an agent a goal, a way to check its own work, and permission to keep trying until it hits that goal. Build. Verify. Repeat. Stop when the condition is met. Here's what it looks like in practice: 1/SEO loop You're position 30 for a term you want. The loop runs once a month, makes changes, checks where you rank, and keeps pushing until you're on page one. This is running in production right now on Inbox Zero. 2/Ads loop You're spending $100 a day and losing money. The loop tests creative, checks profitability, kills what fails, and keeps going until the account is in the black. 3/Eval loop Your AI feature is only 88% accurate. The loop keeps adjusting the prompt and swapping the model until it passes 90%. 4/LLM visibility loop People search in ChatGPT now, not just Google. Same loop, new scoreboard. Are we the answer or not? The whole thing hinges on one thing: a metric that comes back black and white. Where do I rank? Did it hit profitability? Did the evals pass? Give an agent that scoreboard and it runs for months. Loops used to run for 30 minutes. These run for a year. Take a step, sleep, wake up next month, take another one. You're basically hiring an agency that never sleeps, gets paid in tokens instead of invoices, and undoes its own mistakes when the number goes down. Full episode on The Startup Ideas Podcast (SIP) 🧃 watch
39:43

HOW TO USE AI LOOPS TO RUN YOUR BUSINESS 24/7 A lot has been written about loop engineering for building products. Almost nothing about using loops to run the business itself. That's the bigger idea. A loop is when you give an agent a goal, a way to check its own work, and permission to keep trying until it hits that goal. Build. Verify. Repeat. Stop when the condition is met. Here's what it looks like in practice: 1/SEO loop You're position 30 for a term you want. The loop runs once a month, makes changes, checks where you rank, and keeps pushing until you're on page one. This is running in production right now on Inbox Zero. 2/Ads loop You're spending $100 a day and losing money. The loop tests creative, checks profitability, kills what fails, and keeps going until the account is in the black. 3/Eval loop Your AI feature is only 88% accurate. The loop keeps adjusting the prompt and swapping the model until it passes 90%. 4/LLM visibility loop People search in ChatGPT now, not just Google. Same loop, new scoreboard. Are we the answer or not? The whole thing hinges on one thing: a metric that comes back black and white. Where do I rank? Did it hit profitability? Did the evals pass? Give an agent that scoreboard and it runs for months. Loops used to run for 30 minutes. These run for a year. Take a step, sleep, wake up next month, take another one. You're basically hiring an agency that never sleeps, gets paid in tokens instead of invoices, and undoes its own mistakes when the number goes down. Full episode on The Startup Ideas Podcast (SIP) 🧃 watch

GREG ISENBERG

82,335 views • 27 days ago

The guy who kicked off the entire "loop engineering" wave Peter Steinberger: "You shouldn't be prompting coding agents anymore. You should be designing loops that prompt your agents." One post. 6.5M views in a week. In this talk he walks the real stack: the agent loop, a verifier that fails its own work and retries, and a loop that rewrites the agent while he sleeps. Worth more than any $500 vibe-coding course. Watch it, then read the full breakdown of the 4 loops below.
17:30

The guy who kicked off the entire "loop engineering" wave Peter Steinberger: "You shouldn't be prompting coding agents anymore. You should be designing loops that prompt your agents." One post. 6.5M views in a week. In this talk he walks the real stack: the agent loop, a verifier that fails its own work and retries, and a loop that rewrites the agent while he sleeps. Worth more than any $500 vibe-coding course. Watch it, then read the full breakdown of the 4 loops below.

dunik

219,841 views • 1 month ago

Introducing Loop The autonomous business manager that runs your outreach, your follow-ups, and your pipeline,while you focus on the work only you can do. Loop doesn't live in your inbox. Your inbox lives in Loop. Reads every lead like a teammate who's been on your team for years Writes the reply, makes the call, chases the deal when email goes cold Pauses the moment a human actually needs to show up Replaces the patchwork of CRMs, outreach tools, and follow-up apps with one system that does the work Stop managing tools. Start running your loop. comment "loop" and we'll send you in. loop
1:23

Introducing Loop The autonomous business manager that runs your outreach, your follow-ups, and your pipeline,while you focus on the work only you can do. Loop doesn't live in your inbox. Your inbox lives in Loop. Reads every lead like a teammate who's been on your team for years Writes the reply, makes the call, chases the deal when email goes cold Pauses the moment a human actually needs to show up Replaces the patchwork of CRMs, outreach tools, and follow-up apps with one system that does the work Stop managing tools. Start running your loop. comment "loop" and we'll send you in. loop

Anushka Singh

12,881 views • 2 months ago

Boris Cherny, the engineer who built Claude Code: "I don't talk to an agent anymore. I talk to a loop" a prompt is one instruction you babysit. a loop is a goal the AI works toward on its own: > it plans > does the work > checks itself > fixes what's weak > and repeats until it's done you step out, the work keeps going that's the shift the best engineers quietly moved to. most people hear a line like that and have no idea what it means in practice this breaks it down without the hype: what a loop actually is, when it's worth building, when it's a money trap, and how to run one yourself today watch his clip, then read the article below
0:40

Boris Cherny, the engineer who built Claude Code: "I don't talk to an agent anymore. I talk to a loop" a prompt is one instruction you babysit. a loop is a goal the AI works toward on its own: > it plans > does the work > checks itself > fixes what's weak > and repeats until it's done you step out, the work keeps going that's the shift the best engineers quietly moved to. most people hear a line like that and have no idea what it means in practice this breaks it down without the hype: what a loop actually is, when it's worth building, when it's a money trap, and how to run one yourself today watch his clip, then read the article below

Dep

20,895 views • 1 month ago

Claude Code creator Boris Cherny: "Verification is the single most important part of closed-loop development" "Companies underinvest in it, and that is the biggest mistake" In a 26-minute talk, Boris breaks down real AI coding loops with Spotify's Chief Engineer: 00:00 - Closed-loop development 08:33 - Why one-shot code generation fails 10:02 - Agentic verifier and PR success rate 12:00 - Verification loops without humans in the loop 14:00 - Tests, skills, CLAUDE.md, and MCP as the loop infrastructure 20:11 - Why consistent codebases make agents work better This one video is worth more than 100 Claude coding setup tutorials Bookmark and watch it today Then read the full guide on loop engineering below
26:31

Claude Code creator Boris Cherny: "Verification is the single most important part of closed-loop development" "Companies underinvest in it, and that is the biggest mistake" In a 26-minute talk, Boris breaks down real AI coding loops with Spotify's Chief Engineer: 00:00 - Closed-loop development 08:33 - Why one-shot code generation fails 10:02 - Agentic verifier and PR success rate 12:00 - Verification loops without humans in the loop 14:00 - Tests, skills, CLAUDE.md, and MCP as the loop infrastructure 20:11 - Why consistent codebases make agents work better This one video is worth more than 100 Claude coding setup tutorials Bookmark and watch it today Then read the full guide on loop engineering below

rari

73,045 views • 23 days ago

Anthropic engineer: «You're not supposed to sit and re-prompt Claude all day. You build one loop, and it does the work while you sleep.» • 00:00 - Build your first agent that runs on its own • 05:02 - The loop that fixes its own mistakes • 16:43 - Why Claude forgets you between chats, and the fix You can learn it in one afternoon. 30 minutes here replace what most people spend a year figuring out. Watch it today, then read the guide on building loops below.
31:18

Anthropic engineer: «You're not supposed to sit and re-prompt Claude all day. You build one loop, and it does the work while you sleep.» • 00:00 - Build your first agent that runs on its own • 05:02 - The loop that fixes its own mistakes • 16:43 - Why Claude forgets you between chats, and the fix You can learn it in one afternoon. 30 minutes here replace what most people spend a year figuring out. Watch it today, then read the guide on building loops below.

Raytar

28,046 views • 29 days ago

This guy explained agent harness, memory, and loop engineering in one video - clearer than most paid courses a raw LLM with no harness is a wild horse. all power, no direction > trace the run -> score it with an LLM -> diagnose the bottleneck -> patch it -> ship it that loop is what lets an agent get sharper on its own, run after run memory + harness + loop engineering + evals - that's the whole stack in one picture watch it, then grab the diagram below
17:43

This guy explained agent harness, memory, and loop engineering in one video - clearer than most paid courses a raw LLM with no harness is a wild horse. all power, no direction > trace the run -> score it with an LLM -> diagnose the bottleneck -> patch it -> ship it that loop is what lets an agent get sharper on its own, run after run memory + harness + loop engineering + evals - that's the whole stack in one picture watch it, then grab the diagram below

Mr. Buzzoni

43,926 views • 5 days ago

📣 Loop Builder for Divi 5 has arrived, and it's one of the most important features to come to Divi in years. Divi's loop builder is unique in its freedom; you can loop anything without being restricted to a static loop module or container.
5:20

📣 Loop Builder for Divi 5 has arrived, and it's one of the most important features to come to Divi in years. Divi's loop builder is unique in its freedom; you can loop anything without being restricted to a static loop module or container.

Elegant Themes

3,093,835 views • 11 months ago

ANTHROPIC'S LEAD ENGINEER LEAKED A $1.2M SYSTEM THAT TURNS ONE ENGINEER INTO A FLEET OF 10 LOOPS your hands were the bottleneck all along - here are 8 steps that change that stop writing, start delegating - loop: feature, loop: bugfix, loop: tests - each runs independently and ships in parallel CLAUDE.md is law - every agent reads one file before acting - ten agents, one voice, zero chaos Opus 5 breaks the task into 3 independent subtasks - a bad plan multiplied by 10 workers equals 10 disasters each agent gets an isolated git worktree - three features land in the repo while you review one crash at hour 3 means resume at hour 3 not zero - without this you lose hours every day every loop writes its findings to the shared graph - worker 3 never repeats worker 1's dead end at night CLAUDE.md patches itself based on failures - tomorrow the fleet wakes up smarter save this and paste into Claude Code - and your first fleet of 10 loops is already running
0:54

ANTHROPIC'S LEAD ENGINEER LEAKED A $1.2M SYSTEM THAT TURNS ONE ENGINEER INTO A FLEET OF 10 LOOPS your hands were the bottleneck all along - here are 8 steps that change that stop writing, start delegating - loop: feature, loop: bugfix, loop: tests - each runs independently and ships in parallel CLAUDE.md is law - every agent reads one file before acting - ten agents, one voice, zero chaos Opus 5 breaks the task into 3 independent subtasks - a bad plan multiplied by 10 workers equals 10 disasters each agent gets an isolated git worktree - three features land in the repo while you review one crash at hour 3 means resume at hour 3 not zero - without this you lose hours every day every loop writes its findings to the shared graph - worker 3 never repeats worker 1's dead end at night CLAUDE.md patches itself based on failures - tomorrow the fleet wakes up smarter save this and paste into Claude Code - and your first fleet of 10 loops is already running

Sprytix

61,481 views • 13 days ago

i watched gemma 4 12b build something genuinely impressive today, and then loop itself to death right in front of me. the full run is in the video, sped up but completely uncut, watch it to the end and you will catch the exact moment it stops building and starts looping right in the middle of the work. the task was clean, build a single file gravity simulator, n-body physics, orbits, collisions, running locally on one 3090 through an agent. and for ten minutes it was a joy to watch. it reached for a symplectic integrator on its own, the correct one, the kind that keeps orbits stable instead of spiralling out. real gravity with softening, proper orbital velocities, momentum conserved on collision. the physics was right. the thing actually worked. then on the very last step, writing a few tests to prove its own code, it fell into a loop. not a crash, a loop. it started repeating itself and would not stop. ten more minutes, thirty four thousand tokens into a single answer, the same fragments over and over, until i killed it myself. so it's not that gemma can't code. it did the hard part beautifully. it cannot finish. it cannot hold a long task together without unravelling, and finishing is the entire job in agentic work. here's the part that stings. i run this exact task, same harness, same card, on the chinese open models, qwen especially, and i never see this. they build it, they test it, they stop. every single time. google has the raw capability, you can see it sitting right there in the code, and then the model loops itself to death on a task a 27b from alibaba finishes clean. open weights, apache 2.0, so much to love on paper. i just need it to know when to stop talking.
4:15

i watched gemma 4 12b build something genuinely impressive today, and then loop itself to death right in front of me. the full run is in the video, sped up but completely uncut, watch it to the end and you will catch the exact moment it stops building and starts looping right in the middle of the work. the task was clean, build a single file gravity simulator, n-body physics, orbits, collisions, running locally on one 3090 through an agent. and for ten minutes it was a joy to watch. it reached for a symplectic integrator on its own, the correct one, the kind that keeps orbits stable instead of spiralling out. real gravity with softening, proper orbital velocities, momentum conserved on collision. the physics was right. the thing actually worked. then on the very last step, writing a few tests to prove its own code, it fell into a loop. not a crash, a loop. it started repeating itself and would not stop. ten more minutes, thirty four thousand tokens into a single answer, the same fragments over and over, until i killed it myself. so it's not that gemma can't code. it did the hard part beautifully. it cannot finish. it cannot hold a long task together without unravelling, and finishing is the entire job in agentic work. here's the part that stings. i run this exact task, same harness, same card, on the chinese open models, qwen especially, and i never see this. they build it, they test it, they stop. every single time. google has the raw capability, you can see it sitting right there in the code, and then the model loops itself to death on a task a 27b from alibaba finishes clean. open weights, apache 2.0, so much to love on paper. i just need it to know when to stop talking.

Sudo su

39,574 views • 2 months ago

ChatGPT can write you a thousand trading strategies from one sentence. 999 will quietly bleed your account dry. Every single one of them looks like a winner. One method pulls the real one out. Quant desks have run it for years. It's called loop engineering. It's not a smarter prompt. It's a loop: generate a strategy, test it, score why it failed, feed that back, and run it again until one survives data it has never seen. Man Group runs $150 billion. They built an AI that writes and tests hundreds of strategies a week. And second agent whose only job is to hunt the ones that secretly overfit and kill them before a cent goes live. > describe an idea -> backtest 5 years in 12 seconds > read why it died -> feed that back in > run it again until one survives data it never saw AI can write a thousand strategies. Loop engineering is the only thing that tells you which one was ever real. 89% of retail lost money in 2025. Almost none of it from bad ideas. All of it from trading the first guess and never running it through backtest loop. Horizon just put the whole thing in a chat box, free while the beta's open: You're not losing to smarter traders. You're losing to the ones who opened the tab. Anyone can generate a strategy now. Almost no one runs the loop that proves it. That gap is the whole edge. You'll mean to check it later. Later is a "waitlist closed" page.
0:43

ChatGPT can write you a thousand trading strategies from one sentence. 999 will quietly bleed your account dry. Every single one of them looks like a winner. One method pulls the real one out. Quant desks have run it for years. It's called loop engineering. It's not a smarter prompt. It's a loop: generate a strategy, test it, score why it failed, feed that back, and run it again until one survives data it has never seen. Man Group runs $150 billion. They built an AI that writes and tests hundreds of strategies a week. And second agent whose only job is to hunt the ones that secretly overfit and kill them before a cent goes live. > describe an idea -> backtest 5 years in 12 seconds > read why it died -> feed that back in > run it again until one survives data it never saw AI can write a thousand strategies. Loop engineering is the only thing that tells you which one was ever real. 89% of retail lost money in 2025. Almost none of it from bad ideas. All of it from trading the first guess and never running it through backtest loop. Horizon just put the whole thing in a chat box, free while the beta's open: You're not losing to smarter traders. You're losing to the ones who opened the tab. Anyone can generate a strategy now. Almost no one runs the loop that proves it. That gap is the whole edge. You'll mean to check it later. Later is a "waitlist closed" page.

cvxv666

173,703 views • 1 month ago

Jane Street spent $6 billion and 4,032 GPUs on one thing: AI agents that loop through trading strategies 100x faster than any human. Generate, backtest, kill, repeat - thousands a week, until one survives data it's never seen. That loop is why they made $39.6 billion last year while 89% of retail went broke trading one idea they never stress-tested. The edge was never a smarter idea. It was volume. They test 100 strategies for every 1 you test by hand, and a second agent kills the 97 that only look good on old data before a dollar goes live. Now the entire loop fits in a chat box. Horizon takes one plain-English sentence and spins up the same two agents. One builds your strategy, one tries to kill it - backtests 5 years in seconds, and only what survives goes live on your exchange. The $150 billion setup. Free while beta open. Bookmark this & read the full breakdown below - the exact two-agent loop, step by step, and who just handed it to retail.
0:46

Jane Street spent $6 billion and 4,032 GPUs on one thing: AI agents that loop through trading strategies 100x faster than any human. Generate, backtest, kill, repeat - thousands a week, until one survives data it's never seen. That loop is why they made $39.6 billion last year while 89% of retail went broke trading one idea they never stress-tested. The edge was never a smarter idea. It was volume. They test 100 strategies for every 1 you test by hand, and a second agent kills the 97 that only look good on old data before a dollar goes live. Now the entire loop fits in a chat box. Horizon takes one plain-English sentence and spins up the same two agents. One builds your strategy, one tries to kill it - backtests 5 years in seconds, and only what survives goes live on your exchange. The $150 billion setup. Free while beta open. Bookmark this & read the full breakdown below - the exact two-agent loop, step by step, and who just handed it to retail.

cvxv666

317,059 views • 1 month ago

A TURING AWARD WINNER STOOD UP AND TOLD A ROOM OF ENGINEERS THAT ALMOST NONE OF THEM DO THE ONE THING THAT ACTUALLY SEPARATES REAL ENGINEERING FROM TYPING, THEY WRITE CODE BUT THEY NEVER WRITE THE BLUEPRINT 56 minutes from Leslie Lamport -- Turing Award winner, creator of the tech behind almost every distributed system on earth. -> His claim: architects draw plans before a brick is laid. Programmers just start coding and hope. That gap is where complex systems quietly break. 04:10 -- A blueprint for software is called a spec. Write what the system must DO before touching how it does it. 10:13 -- Thinking above the code is the skill. The language is just the last, easiest step. 43:23 -- What programmers should really know isn't syntax. It's thinking clearly enough that "done" actually means done. 48:15 -- Thinking is hard, so we skip it. We jump straight to code because typing feels like progress. And this is exactly the wall the new "Loop engineering" hype is about to hit -- people now design loops of agents that write and check code while they walk away. But an unattended loop with no spec just ships broken work faster. Lamport is the missing half: the discipline that makes it safe to leave a loop running at all. You thought the leverage moved into better prompts and better loops. This is the man showing it moved above the code, where almost no one is willing to think. Save this. Read it before you trust a single agent loop ↓
56:47

A TURING AWARD WINNER STOOD UP AND TOLD A ROOM OF ENGINEERS THAT ALMOST NONE OF THEM DO THE ONE THING THAT ACTUALLY SEPARATES REAL ENGINEERING FROM TYPING, THEY WRITE CODE BUT THEY NEVER WRITE THE BLUEPRINT 56 minutes from Leslie Lamport -- Turing Award winner, creator of the tech behind almost every distributed system on earth. -> His claim: architects draw plans before a brick is laid. Programmers just start coding and hope. That gap is where complex systems quietly break. 04:10 -- A blueprint for software is called a spec. Write what the system must DO before touching how it does it. 10:13 -- Thinking above the code is the skill. The language is just the last, easiest step. 43:23 -- What programmers should really know isn't syntax. It's thinking clearly enough that "done" actually means done. 48:15 -- Thinking is hard, so we skip it. We jump straight to code because typing feels like progress. And this is exactly the wall the new "Loop engineering" hype is about to hit -- people now design loops of agents that write and check code while they walk away. But an unattended loop with no spec just ships broken work faster. Lamport is the missing half: the discipline that makes it safe to leave a loop running at all. You thought the leverage moved into better prompts and better loops. This is the man showing it moved above the code, where almost no one is willing to think. Save this. Read it before you trust a single agent loop ↓

slash1s

15,306 views • 23 days ago

Demis Hassabis confirmed every frontier AI lab is working on recursive self-improvement and in the same sentence said the safety risk of removing humans from the loop entirely keeps him up at night. That combination should stop you. The CEO of Google DeepMind just confirmed that the thing most people treat as a theoretical future risk is already the active focus of every serious lab on earth right now. He explained why it works in coding and math. The feedback loop is fast. You can verify whether an answer is correct almost instantly. You can generate synthetic training data from it. The loop closes quickly and cleanly. Then he said where it breaks down. In biology, chemistry and physics. Any domain where verifying a hypothesis requires a physical experiment in the real world. The loop does not close in seconds. It closes in weeks or months. Geoffrey Hinton said in his Nobel lecture that recursive self-improvement is the development he fears most and that once started it may not be possible to stop. Hassabis is not pushing back on that. He is describing the guardrails labs are building around a process they are already running. Every lab has to think carefully about the safety of a process where no human is in the loop. He said that as a constraint they are navigating right now. The question they are sitting with is how much of it to let run without a human watching. (Watch the full interview on YouTube at Two Minute Papers channel)
2:00

Demis Hassabis confirmed every frontier AI lab is working on recursive self-improvement and in the same sentence said the safety risk of removing humans from the loop entirely keeps him up at night. That combination should stop you. The CEO of Google DeepMind just confirmed that the thing most people treat as a theoretical future risk is already the active focus of every serious lab on earth right now. He explained why it works in coding and math. The feedback loop is fast. You can verify whether an answer is correct almost instantly. You can generate synthetic training data from it. The loop closes quickly and cleanly. Then he said where it breaks down. In biology, chemistry and physics. Any domain where verifying a hypothesis requires a physical experiment in the real world. The loop does not close in seconds. It closes in weeks or months. Geoffrey Hinton said in his Nobel lecture that recursive self-improvement is the development he fears most and that once started it may not be possible to stop. Hassabis is not pushing back on that. He is describing the guardrails labs are building around a process they are already running. Every lab has to think carefully about the safety of a process where no human is in the loop. He said that as a constraint they are navigating right now. The question they are sitting with is how much of it to let run without a human watching. (Watch the full interview on YouTube at Two Minute Papers channel)

Ihtesham Ali

68,231 views • 1 month ago

ANTHROPIC LEAKED 6 RULES THAT RUN 8 LOOPS AT ONCE - AND ONE ENGINEER DOES THE WORK OF A TEAM one engineer with this system replaces an entire team - and costs the company 8 times less You → Opus 5 plan → Fable 5 ×8 execute → Fable 5 review → you: 5 min Opus 5 takes your intent and breaks it into subtasks - a bad plan multiplied across every loop gives the same number of disasters - the plan is the only thing you read carefully one repo - isolated worktrees for each loop - nobody stands on anyone's file - parallel PRs ship while you do nothing the agent runs the tests and fixes until green PR - a red build never reaches your eyes one CLAUDE.md for the whole fleet - without it you get different opinions from every loop and one merge hell the average engineer closes 3-4 tasks a day - this system closes a full sprint overnight with zero working hours Fable 5 pre-reviews every PR before it reaches you - you spend 5 minutes - your throughput is now measured in diffs read per hour bookmark and paste into Claude Code - your first fleet can start tonight
1:15

ANTHROPIC LEAKED 6 RULES THAT RUN 8 LOOPS AT ONCE - AND ONE ENGINEER DOES THE WORK OF A TEAM one engineer with this system replaces an entire team - and costs the company 8 times less You → Opus 5 plan → Fable 5 ×8 execute → Fable 5 review → you: 5 min Opus 5 takes your intent and breaks it into subtasks - a bad plan multiplied across every loop gives the same number of disasters - the plan is the only thing you read carefully one repo - isolated worktrees for each loop - nobody stands on anyone's file - parallel PRs ship while you do nothing the agent runs the tests and fixes until green PR - a red build never reaches your eyes one CLAUDE.md for the whole fleet - without it you get different opinions from every loop and one merge hell the average engineer closes 3-4 tasks a day - this system closes a full sprint overnight with zero working hours Fable 5 pre-reviews every PR before it reaches you - you spend 5 minutes - your throughput is now measured in diffs read per hour bookmark and paste into Claude Code - your first fleet can start tonight

Sprytix

37,766 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.
0:37

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 • 1 month ago

THIS GUY CONNECTED CLAUDE TO TRADINGVIEW AND CUT 200+ HOURS OF MANUAL CHART WORK 40 trades a week used to mean the same loop: open the chart, check RSI, compare EMA, write notes and wait for the next setup now Claude reads TradingView 24/7, tracks volume, indicators and price conditions while he is not even at the desk this is not a $20k trading terminal and not a quant fund setup, just one laptop, one chart and one strategy written in plain English the crazy part is not that Claude predicts the market, it is that a regular trader can remove the boring human loop from every setup ↓
0:26

THIS GUY CONNECTED CLAUDE TO TRADINGVIEW AND CUT 200+ HOURS OF MANUAL CHART WORK 40 trades a week used to mean the same loop: open the chart, check RSI, compare EMA, write notes and wait for the next setup now Claude reads TradingView 24/7, tracks volume, indicators and price conditions while he is not even at the desk this is not a $20k trading terminal and not a quant fund setup, just one laptop, one chart and one strategy written in plain English the crazy part is not that Claude predicts the market, it is that a regular trader can remove the boring human loop from every setup ↓

Gipp 🦅

55,610 views • 2 months ago

Today we're introducing Wave. A proactive product agent that helps teams build self-improving products. Every product team runs the same loop. Build, ship, use, learn. AI has made building and shipping extraordinarily fast. Understanding usage and learning still happen by hand. Wave runs the whole loop: - Analyzes your Amplitude data for signals across analytics, feedback, session replays, error logs, agent traces, and experiment results - Surfaces opportunities in the form of full product specs that you or your agents can approve and ship - Tracks the experiments and outcomes of what you've built so you can start the loop over again Your product learns what works and gets smarter every cycle:
2:36

Today we're introducing Wave. A proactive product agent that helps teams build self-improving products. Every product team runs the same loop. Build, ship, use, learn. AI has made building and shipping extraordinarily fast. Understanding usage and learning still happen by hand. Wave runs the whole loop: - Analyzes your Amplitude data for signals across analytics, feedback, session replays, error logs, agent traces, and experiment results - Surfaces opportunities in the form of full product specs that you or your agents can approve and ship - Tracks the experiments and outcomes of what you've built so you can start the loop over again Your product learns what works and gets smarter every cycle:

Spenser Skates

111,827 views • 2 months ago