Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

This video will make you an expert loop engineer in 21 minutes. Prompting is dead. You need to be running loops. 0:51 Understanding LLMs 3:41 wtf is a loop? 6:17 Two kinds of loops 8:54 /goal versus /loop 10:44 Website audit demo 13:27 Real loop workflow ideas 19:11 Scheduling loops

Miles Deutscher

678,160 subscribers

168,285 Aufrufe • vor 1 Monat •via X (Twitter)

Wissenschaft & Technologie Bildung

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

This video will make you a Claude Fable 5 expert in 20 minutes. 0:00 Intro 2:43 wtf is a loop? 5:30 Loop Engineering 101 *demo included* 8:12 Fable 5 x Claude Skills 10:10 3 ways to build effective Fable 5 Skills 12:12 Visual capabilities 14:04 Building a local memory system 18:17 How I'm personally using Fable now

This video will make you a Claude Fable 5 expert in 20 minutes. 0:00 Intro 2:43 wtf is a loop? 5:30 Loop Engineering 101 demo included 8:12 Fable 5 x Claude Skills 10:10 3 ways to build effective Fable 5 Skills 12:12 Visual capabilities 14:04 Building a local memory system 18:17 How I'm personally using Fable now

Miles Deutscher

319,969 Aufrufe • vor 2 Monaten

Anthropic just dropped 1-hour workshop on loop engineering: 1 spec → the loop → 200 features from 0% to 100%: • 10% → 5:31 - Building memory for agentic loops • 30% → 8:22 - Four files for each Loop: features.json, standards.md, progress.md, • 55% → 11:02 - The Loop: check environment → run tests → pick feature → build → test → commit • 80% → 13:06 - one feature per loop. try everything at once and context dies mid-build • 100% → 33:03 - MVP in 1 hour, every next loop under 30 minutes most people build an agent that finishes a task -Anthropic ships agentic loops that can run for days without you. watch it today - then read the full loop engineering playbook below ↓

Anthropic just dropped 1-hour workshop on loop engineering: 1 spec → the loop → 200 features from 0% to 100%: • 10% → 5:31 - Building memory for agentic loops • 30% → 8:22 - Four files for each Loop: features.json, standards.md, progress.md, • 55% → 11:02 - The Loop: check environment → run tests → pick feature → build → test → commit • 80% → 13:06 - one feature per loop. try everything at once and context dies mid-build • 100% → 33:03 - MVP in 1 hour, every next loop under 30 minutes most people build an agent that finishes a task -Anthropic ships agentic loops that can run for days without you. watch it today - then read the full loop engineering playbook below ↓

Codez

18,398 Aufrufe • vor 1 Monat

Anthropic engineer: "At Antropic, >80% of our engineers are building with self-improving loops. in 3-6 months, it will be 100%. my agentic loops can run for hours without spending hundreds of $$$." in 30-minute podcast, an Antropic engineer shows how to build the right spec for an agentic loop. Loop + plan + PRDs + spec + markdown - that’s the secret stack. Worth more than a $500 agentic course on the internet. Watch it now, then read how quants are building trading loops from scratch.

Anthropic engineer: "At Antropic, >80% of our engineers are building with self-improving loops. in 3-6 months, it will be 100%. my agentic loops can run for hours without spending hundreds of $$$." in 30-minute podcast, an Antropic engineer shows how to build the right spec for an agentic loop. Loop + plan + PRDs + spec + markdown - that’s the secret stack. Worth more than a $500 agentic course on the internet. Watch it now, then read how quants are building trading loops from scratch.

Movez

282,313 Aufrufe • vor 2 Monaten

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

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,236 Aufrufe • vor 2 Monaten

Amazon AI engineer just explained how to build agentic loops from scratch in under 10-minutes. this is one of the clearest explanations of AI agentic loops you’ll find anywhere. Loop + model + agent + hooks + MCP = an autonomous, self-improving system. People are paying $500 for courses that teach less than this. Watch it, then read the step-by-step guide below on building loops for your own agents.

Amazon AI engineer just explained how to build agentic loops from scratch in under 10-minutes. this is one of the clearest explanations of AI agentic loops you’ll find anywhere. Loop + model + agent + hooks + MCP = an autonomous, self-improving system. People are paying $500 for courses that teach less than this. Watch it, then read the step-by-step guide below on building loops for your own agents.

Codez

26,868 Aufrufe • vor 2 Monaten

The creator of Claude Code deleted his IDE in November 2024. In the last 30 days, 100% of his contributions were written by Claude Code. 259 PRs. His job is not prompting anymore. His job is writing loops that prompt Claude for him. Here is what that progression actually looks like: → stage 1: write code by hand with autocomplete → stage 2: run 5-10 claude sessions in parallel, prompt each one yourself → stage 3: write loops that prompt claude — you become the author, the model becomes a subroutine → the ralph loop (2025): bash one-liner, fixed anchor files, built a programming language for $297 → the 2026 loop: loops supervising loops, scheduling on infrastructure time, git-backed durable state → five building blocks: automations, durable state, validator split, loop orchestration, crash recovery Most developers are still in stage 2, prompting sessions by hand. The ones at stage 3 are writing the loops that do the prompting for them. Read this article to be ahead of the curve! Follow NeilXbt for more AI engineering intelligence that shows you exactly where the leverage moved and what building at that level actually looks like.

The creator of Claude Code deleted his IDE in November 2024. In the last 30 days, 100% of his contributions were written by Claude Code. 259 PRs. His job is not prompting anymore. His job is writing loops that prompt Claude for him. Here is what that progression actually looks like: → stage 1: write code by hand with autocomplete → stage 2: run 5-10 claude sessions in parallel, prompt each one yourself → stage 3: write loops that prompt claude — you become the author, the model becomes a subroutine → the ralph loop (2025): bash one-liner, fixed anchor files, built a programming language for $297 → the 2026 loop: loops supervising loops, scheduling on infrastructure time, git-backed durable state → five building blocks: automations, durable state, validator split, loop orchestration, crash recovery Most developers are still in stage 2, prompting sessions by hand. The ones at stage 3 are writing the loops that do the prompting for them. Read this article to be ahead of the curve! Follow NeilXbt for more AI engineering intelligence that shows you exactly where the leverage moved and what building at that level actually looks like.

NeilXbt

11,556 Aufrufe • vor 3 Monaten

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

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 Aufrufe • vor 1 Monat

NVIDIA CEO, Jensen Huang: "Nobody writes prompts anymore. The new job is to design and manage loops. Self-learning agentic systems powered by loops are what you should be learning right now" in 30-minute talk, 6 greatest minds in AI discuss the skills you need to stay competitive in the AI era. Watch it, then read about Band’s real loop setup in the post below.

NVIDIA CEO, Jensen Huang: "Nobody writes prompts anymore. The new job is to design and manage loops. Self-learning agentic systems powered by loops are what you should be learning right now" in 30-minute talk, 6 greatest minds in AI discuss the skills you need to stay competitive in the AI era. Watch it, then read about Band’s real loop setup in the post below.

Codez

13,865 Aufrufe • vor 2 Monaten

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

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

83,349 Aufrufe • vor 2 Monaten

$Boris Cherny, head of Claude Code at Anthropic: "I don't prompt Claude anymore. I have loops that are running; they are the ones prompting Claude and figuring out what to do. My job is to write loops." He's right. Karpathy and Steinberger arrived at the same conclusion from different angles. The skill has a new name. Loop engineering. Cherny's token bill is zero. He works at Anthropic. Steinberger burned $1.3 million in OpenAI credits in 30 days. He works at OpenAI. Loops are the right architecture. But the people evangelizing them aren't the ones paying. I wrote a breakdown of five plays that land most of what a loop gives you at a fraction of the cost, plus the one case where a loop is worth paying for.$

Boris Cherny, head of Claude Code at Anthropic: "I don't prompt Claude anymore. I have loops that are running; they are the ones prompting Claude and figuring out what to do. My job is to write loops." He's right. Karpathy and Steinberger arrived at the same conclusion from different angles. The skill has a new name. Loop engineering. Cherny's token bill is zero. He works at Anthropic. Steinberger burned $1.3 million in OpenAI credits in 30 days. He works at OpenAI. Loops are the right architecture. But the people evangelizing them aren't the ones paying. I wrote a breakdown of five plays that land most of what a loop gives you at a fraction of the cost, plus the one case where a loop is worth paying for.

Alex Prompter

15,166 Aufrufe • vor 2 Monaten

Boris Cherny, Head of Claude Code at Anthropic: "I do not prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops." The person who built the most used AI coding tool stopped prompting entirely. Most people using it every day are still typing one request at a time. This Github repo changes that. ↳ Seven production loop patterns with real token cost estimates ↳ CLI that scaffolds your entire loop in five minutes ↳ Starters for Grok, Claude Code, Codex, and Opencode The repo gives you the framework. My article covers the mental shift that makes it actually work.

Boris Cherny, Head of Claude Code at Anthropic: "I do not prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops." The person who built the most used AI coding tool stopped prompting entirely. Most people using it every day are still typing one request at a time. This Github repo changes that. ↳ Seven production loop patterns with real token cost estimates ↳ CLI that scaffolds your entire loop in five minutes ↳ Starters for Grok, Claude Code, Codex, and Opencode The repo gives you the framework. My article covers the mental shift that makes it actually work.

Kanika

20,656 Aufrufe • vor 1 Monat

The future of vibecoding is looping. ( my recent app cnvs has done $5.7k in 5 days and was made primarily with design looping ) you can easily break free from ai slop and create designs that feel artisan and worth paying for. im begging you to bookmark this 10 min beginner guide and start setting up loops, it will change everything for you. Timestamps : 0:27 – The ultra-simple looping diagram explained 1:18 – The best loop to start with: the design loop 1:38 – Using Codex + GPT Image Gen for the mockup 3:57 – Handing the mockup to Claude Code 4:45 – Loop starts (screenshot → compare → iterate) 7:31 – Loop finished : reviewing the result

The future of vibecoding is looping. ( my recent app cnvs has done $5.7k in 5 days and was made primarily with design looping ) you can easily break free from ai slop and create designs that feel artisan and worth paying for. im begging you to bookmark this 10 min beginner guide and start setting up loops, it will change everything for you. Timestamps : 0:27 – The ultra-simple looping diagram explained 1:18 – The best loop to start with: the design loop 1:38 – Using Codex + GPT Image Gen for the mockup 3:57 – Handing the mockup to Claude Code 4:45 – Loop starts (screenshot → compare → iterate) 7:31 – Loop finished : reviewing the result

Max Blade

22,493 Aufrufe • vor 3 Monaten

ANTHROPIC LEAKED A 6-LOOP SETUP THAT REPLACES A $3,000 AGENCY AND COSTS $59 A MONTH Microsoft and Google have been running this for a while - the gap against an agency is exactly 51x. an agency charged you for waiting, not for work - the brief walked from the strategist to the copywriter to the designer for weeks. here all 6 loops read one file on the same pass - there's nobody to wait on, and the calendar is empty. 51% of the bill is production on Sonnet 5, and only 5% is strategy on Opus 5 - the priciest model runs once a week. 22% of the whole bill sits on the batch queue at half rate - where nobody is waiting for an answer right now. the journal is the only loop that writes back into the root - which angle is dead, and next week starts tighter. the 6 loops bring you 3 angles a week - the final pick stays yours, and that's the part that never automates. save this and paste it into Claude Code - the loops remove the waiting, not the judgement ↓

ANTHROPIC LEAKED A 6-LOOP SETUP THAT REPLACES A $3,000 AGENCY AND COSTS $59 A MONTH Microsoft and Google have been running this for a while - the gap against an agency is exactly 51x. an agency charged you for waiting, not for work - the brief walked from the strategist to the copywriter to the designer for weeks. here all 6 loops read one file on the same pass - there's nobody to wait on, and the calendar is empty. 51% of the bill is production on Sonnet 5, and only 5% is strategy on Opus 5 - the priciest model runs once a week. 22% of the whole bill sits on the batch queue at half rate - where nobody is waiting for an answer right now. the journal is the only loop that writes back into the root - which angle is dead, and next week starts tighter. the 6 loops bring you 3 angles a week - the final pick stays yours, and that's the part that never automates. save this and paste it into Claude Code - the loops remove the waiting, not the judgement ↓

Noisy

10,557 Aufrufe • vor 24 Tagen

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,637 Aufrufe • vor 2 Monaten

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

153,908 Aufrufe • vor 2 Monaten

Сreator of Claude Code: BORIS CHERNY, WHO BUILT CLAUDE CODE, SAID IT PLAINLY." 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. "He is not typing anymore. He runs loops that write the code for him. That is the shift most people miss. Not a better prompt. A loop that keeps running while you are gone.People sell $500 courses on this. The person who built the tool said it for free. The exact setup is in the article below.Bookmark this. Follow CyrilXBT

Сreator of Claude Code: BORIS CHERNY, WHO BUILT CLAUDE CODE, SAID IT PLAINLY." 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. "He is not typing anymore. He runs loops that write the code for him. That is the shift most people miss. Not a better prompt. A loop that keeps running while you are gone.People sell $500 courses on this. The person who built the tool said it for free. The exact setup is in the article below.Bookmark this. Follow CyrilXBT

CyrilXBT

38,772 Aufrufe • vor 2 Monaten

Less than two weeks before he left Google to co-found Discovery Loop, Jeff Dean described the automated research loop the new company is named for, giving no hint he was about to leave to go do it. "There's this sort of the foundation of the scientific method of you propose an experiment, you implement what you need to run the experiment, and you evaluate the experiment, and then you get results from that." "And I think there are more and more problems that are now possible to implement where that whole loop of running not just a few experiments, but running many, many experiments because you're able to automate that loop and make the latency of that loop extremely low is going to be really, really important." "It's going to enable us to tackle lots of different problem domains in science and engineering and machine learning, model design itself, and also in engineering tasks like designing chips."

Less than two weeks before he left Google to co-found Discovery Loop, Jeff Dean described the automated research loop the new company is named for, giving no hint he was about to leave to go do it. "There's this sort of the foundation of the scientific method of you propose an experiment, you implement what you need to run the experiment, and you evaluate the experiment, and then you get results from that." "And I think there are more and more problems that are now possible to implement where that whole loop of running not just a few experiments, but running many, many experiments because you're able to automate that loop and make the latency of that loop extremely low is going to be really, really important." "It's going to enable us to tackle lots of different problem domains in science and engineering and machine learning, model design itself, and also in engineering tasks like designing chips."

Fireside Alpha

14,495 Aufrufe • vor 1 Monat

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

844,159 Aufrufe • vor 2 Monaten

FOUR TYPES OF AGENT LOOPS. LOOP ENGINEERING IS PICKING THE RIGHT ONE, NOT THE FANCIEST ONE every loop answers two questions: what starts a run, what ends it hand-run, you answer both yourself, every time 1) turn-based > you prompt, it acts, you review, you prompt again > use while requirements are still forming 2) goal-based > /goal hit Lighthouse 90, stop after 5 tries > an evaluator checks. a no sends it back to work > use when the outcome is measurable but the path isn't 3) time-based > a clock fires, it checks the PR, fixes CI, waits again > /loop runs locally, /schedule survives a closed laptop > use for anything recurring 4) proactive > no human present. it watches a channel, triages, fixes, reviews, closes the task itself > use for standing duties you can't predict in advance the real question isn't which loop is most advanced it's whether your task is exploratory, measurable, recurring, or standing the more you hand off, the less you babysit full breakdown in the article below

FOUR TYPES OF AGENT LOOPS. LOOP ENGINEERING IS PICKING THE RIGHT ONE, NOT THE FANCIEST ONE every loop answers two questions: what starts a run, what ends it hand-run, you answer both yourself, every time 1) turn-based > you prompt, it acts, you review, you prompt again > use while requirements are still forming 2) goal-based > /goal hit Lighthouse 90, stop after 5 tries > an evaluator checks. a no sends it back to work > use when the outcome is measurable but the path isn't 3) time-based > a clock fires, it checks the PR, fixes CI, waits again > /loop runs locally, /schedule survives a closed laptop > use for anything recurring 4) proactive > no human present. it watches a channel, triages, fixes, reviews, closes the task itself > use for standing duties you can't predict in advance the real question isn't which loop is most advanced it's whether your task is exploratory, measurable, recurring, or standing the more you hand off, the less you babysit full breakdown in the article below

Fokki

10,312 Aufrufe • vor 1 Monat

Anthropic engineer: "85% of our engineers are using self-improving loops. Now everyone is running agentic Graphs. In 3-6 months, we’ll all be building graphs to orchestrate agents. No more prompting." In a 45-minute talk, an Anthropic engineer shows how to build a self-improving agentic workflow from scratch. Worth more than a $500 agentic course. Watch this video, then read the full roadmap on how to become a graph architect in the article below

Anthropic engineer: "85% of our engineers are using self-improving loops. Now everyone is running agentic Graphs. In 3-6 months, we’ll all be building graphs to orchestrate agents. No more prompting." In a 45-minute talk, an Anthropic engineer shows how to build a self-improving agentic workflow from scratch. Worth more than a $500 agentic course. Watch this video, then read the full roadmap on how to become a graph architect in the article below

Codez

36,774 Aufrufe • vor 1 Monat