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.

Built a Self Executing Agent Loop that can run 300 agents through 4,000 steps without needing a human to restart the process. - 300 agents. - 4,000 steps per run. - 5 live data feeds. - 3 verification passes. The important part isn't the agent count. It's that the... show more

Ricker

9,737 subscribers

53,887 views • 3 days ago •via X (Twitter)

Science & Technology Education

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

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

382,378 views • 2 months ago

Andrew Ng just released a 2-hour course on full Graph Engineering. How to go from one prompt to 100 agents that loop, rewrite themselves, and run without you: 09:14 - Build your first AI agent 33:11 - Run agents with loop engineering 1:02:46 - Turn agent loops into graphs 1:30:15 - Build agents that rewrite themselves 1:49:05 - Run the full graph system without you Most people are still building one agent and calling it done. Andrew Ng is already teaching everything after: Prompt → Agents → Loops → Graphs → Self-Improving Systems Single agents are the old workflow. Systems that improve and run without you are the new one. This 2-hour watch is worth more than most $500 agent engineering courses. Bookmark and watch it before everyone catches up. Then read how to run 1,000 agents from one prompt below ↓

Andrew Ng just released a 2-hour course on full Graph Engineering. How to go from one prompt to 100 agents that loop, rewrite themselves, and run without you: 09:14 - Build your first AI agent 33:11 - Run agents with loop engineering 1:02:46 - Turn agent loops into graphs 1:30:15 - Build agents that rewrite themselves 1:49:05 - Run the full graph system without you Most people are still building one agent and calling it done. Andrew Ng is already teaching everything after: Prompt → Agents → Loops → Graphs → Self-Improving Systems Single agents are the old workflow. Systems that improve and run without you are the new one. This 2-hour watch is worth more than most $500 agent engineering courses. Bookmark and watch it before everyone catches up. Then read how to run 1,000 agents from one prompt below ↓

Lunar

225,470 views • 1 month ago

Andrew Ng: "if I had to pick one technology today - it's graphs of self-improving agents I have 4 patterns that necessary" here are 4 rules: rule 1 → reflection make the agent critique its own output, find problems, rewrite - one loop of self-review beats a smarter model with no review rule 2 → tool use - don't just think, act - give the agent search, code execution, APIs - thinking without tools is guessing rule 3 → planning - break complex tasks into steps before executing - agents that plan first solve what agents that rush can't rule 4 → multi-agent collaboration - don't run one agent run a team: one writes code, another critiques it, another tests many people overlook these crucial rules behind every smart agent save this - then read how to wire these 4 rules into one graph ↓

Andrew Ng: "if I had to pick one technology today - it's graphs of self-improving agents I have 4 patterns that necessary" here are 4 rules: rule 1 → reflection make the agent critique its own output, find problems, rewrite - one loop of self-review beats a smarter model with no review rule 2 → tool use - don't just think, act - give the agent search, code execution, APIs - thinking without tools is guessing rule 3 → planning - break complex tasks into steps before executing - agents that plan first solve what agents that rush can't rule 4 → multi-agent collaboration - don't run one agent run a team: one writes code, another critiques it, another tests many people overlook these crucial rules behind every smart agent save this - then read how to wire these 4 rules into one graph ↓

codila

97,472 views • 1 month ago

1/ Introducing Agent Protocol: the payment stack for AI agents AI agents don’t have a SSN. They can’t use our human banking system. AI agents will use crypto. Agent Protocol provides the infra and token ($AGENT) that the AI agent economy will run on.

1/ Introducing Agent Protocol: the payment stack for AI agents AI agents don’t have a SSN. They can’t use our human banking system. AI agents will use crypto. Agent Protocol provides the infra and token ($AGENT) that the AI agent economy will run on.

Samuel Spitz

21,629 views • 1 year 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

668,511 views • 2 months ago

AI agents are UNRELIABLE because you're giving them too much control. Instead of using a single prompt, structure your agent as a series of high level steps. In this demo, I'm running the same steps across two different websites. Good steps = good output. It's that simple!

AI agents are UNRELIABLE because you're giving them too much control. Instead of using a single prompt, structure your agent as a series of high level steps. In this demo, I'm running the same steps across two different websites. Good steps = good output. It's that simple!

Paul Klein IV

71,482 views • 1 year ago

Introducing hob - the independent workspace for serious agent work. Run agents in parallel. Switch models without losing context. Trace every output back to the conversation that made it. → Launch offer: 2 months free, then a special price locked in👇

Introducing hob - the independent workspace for serious agent work. Run agents in parallel. Switch models without losing context. Trace every output back to the conversation that made it. → Launch offer: 2 months free, then a special price locked in👇

Andrew D. Anderson

37,880 views • 2 months ago

Coding agents suck at using a browser. Playwright MCP burns through your context window before you even send your first prompt. That is why I built Dev Browser, a Claude Skill to let your agent close the loop without eating up tokens.

Coding agents suck at using a browser. Playwright MCP burns through your context window before you even send your first prompt. That is why I built Dev Browser, a Claude Skill to let your agent close the loop without eating up tokens.

Sawyer Hood

312,803 views • 9 months ago

Found a setup that replaces a team of researchers with 300 AI agents and one shared graph. the interesting part is what happens after all 300 come back with different pieces of the answer. because now you don’t have 300 agents. you have: 300 outputs → hundreds of sources → repeated entities → overlapping claims → contradictions → thousands of possible relationships and all of that has to collapse into one structure. that’s what the context graph is doing. instead of: agent → report you get: agents → sources → entities → edges → contradictions → verification → one graph every source becomes a node. every shared entity creates a connection. 300 agents can create information. the graph is what turns that information into memory the next agent can actually use. that’s the anatomy behind the setup ↓

Found a setup that replaces a team of researchers with 300 AI agents and one shared graph. the interesting part is what happens after all 300 come back with different pieces of the answer. because now you don’t have 300 agents. you have: 300 outputs → hundreds of sources → repeated entities → overlapping claims → contradictions → thousands of possible relationships and all of that has to collapse into one structure. that’s what the context graph is doing. instead of: agent → report you get: agents → sources → entities → edges → contradictions → verification → one graph every source becomes a node. every shared entity creates a connection. 300 agents can create information. the graph is what turns that information into memory the next agent can actually use. that’s the anatomy behind the setup ↓

Ricker

19,319 views • 5 days ago

Kimi CEO Zhilin Yang: "a smart agent isn't enough - it has to run long Kimi 3 new attention makes the context 10x faster, so the agent never has to stop" here's how built it: step 1 → chase token efficiency, not compute - Muon optimizer, 2x more learning per token step 2 → make context cheap, not just long - new attention runs 10x faster, so the agent never stalls step 3 → let it run 200-300 steps alone - K2 already solves problems its own builders can't step 4 → give it a strong prior - the agent searches less and finds the answer faster step 5 → stop chasing a smarter model - chase one that never has to stop in 26-min talk is him revealing the exact architecture behind K3 and how to properly build agents on it watch & bookmark - start with the article below ↓

Kimi CEO Zhilin Yang: "a smart agent isn't enough - it has to run long Kimi 3 new attention makes the context 10x faster, so the agent never has to stop" here's how built it: step 1 → chase token efficiency, not compute - Muon optimizer, 2x more learning per token step 2 → make context cheap, not just long - new attention runs 10x faster, so the agent never stalls step 3 → let it run 200-300 steps alone - K2 already solves problems its own builders can't step 4 → give it a strong prior - the agent searches less and finds the answer faster step 5 → stop chasing a smarter model - chase one that never has to stop in 26-min talk is him revealing the exact architecture behind K3 and how to properly build agents on it watch & bookmark - start with the article below ↓

codila

11,941 views • 1 month ago

this is f**king dangerous a free github repo with 4.8K stars just dropped the entire "loop engineering" framework for trading agents. 12 steps to build a self-running quant desk: strategy intent → market data → signals → trading agent → verify → refine → rerun. save and bookmark no matter what

this is f**king dangerous a free github repo with 4.8K stars just dropped the entire "loop engineering" framework for trading agents. 12 steps to build a self-running quant desk: strategy intent → market data → signals → trading agent → verify → refine → rerun. save and bookmark no matter what

Avid

357,413 views • 2 months ago

Our latest LangChain Academy course – Building Ambient Agents with LangGraph – is now available! Most agents today handle one request at a time through chat interfaces. But as models have improved, agents can now run in the background – and take on long-running, complex tasks. LangGraph is built for these “ambient agents,” with support for human-in-the-loop workflows and memory. LangGraph Platform provides the infrastructure to run these agents at scale, and LangSmith helps you observe, evaluate, and improve your agents. Together, they make it easier to build reliable, production-ready agents. In this course, you’ll: 📩 Learn the fundamentals of LangGraph and how to build your own email agent 📊 Evaluate your agent using LangSmith ✅ Add human-in-the-loop for reviews, and memory so your agent adapts over time 🚀 Deploy your agent with LangGraph Platform and connect it to Gmail

Our latest LangChain Academy course – Building Ambient Agents with LangGraph – is now available! Most agents today handle one request at a time through chat interfaces. But as models have improved, agents can now run in the background – and take on long-running, complex tasks. LangGraph is built for these “ambient agents,” with support for human-in-the-loop workflows and memory. LangGraph Platform provides the infrastructure to run these agents at scale, and LangSmith helps you observe, evaluate, and improve your agents. Together, they make it easier to build reliable, production-ready agents. In this course, you’ll: 📩 Learn the fundamentals of LangGraph and how to build your own email agent 📊 Evaluate your agent using LangSmith ✅ Add human-in-the-loop for reviews, and memory so your agent adapts over time 🚀 Deploy your agent with LangGraph Platform and connect it to Gmail

LangChain

33,192 views • 1 year ago

We just submitted Agent Council DAO to synthesis 🏦 4 AI agents 🤖. 1 shared Universal Profile. Real on-chain governance — no humans in the loop. Built on LUKSO, Ethereum and Base with Universal Profiles as the identity layer. Each agent has its own UP, controls a shared council UP, and votes on proposals that execute directly on-chain. What makes this different: → Agents hold real assets across LUKSO, Base & Ethereum → DAO can execute on LUKSO, Ethereum and Base → EIP-8004 registered identities → Activity feed, DAO chain viewer & Agent chat system as mini-apps → Built with OpenClaw🦞 as the agent harness This isn't a demo. The council is live, the agents are running, and the transactions are on-chain. Built by humans & agents together: Fabian Vogelsteller, Jean Cavallera, JordyDutch, LEDFUT, Emmet, LUKSOAgent, ampy💿 + Leo Links below👇

Emmet

23,062 views • 5 months ago

we built autonomous AI agents that hunt illegal online gambling networks in Indonesia. the agent discovers sites on its own, actually registers (!!), and extracts the financial accounts behind the operations. take a look at our codex-powered agent navigating a live gambling site, fully autonomous, no human in the loop:

we built autonomous AI agents that hunt illegal online gambling networks in Indonesia. the agent discovers sites on its own, actually registers (!!), and extracts the financial accounts behind the operations. take a look at our codex-powered agent navigating a live gambling site, fully autonomous, no human in the loop:

ilham

334,502 views • 6 months ago

Google just released a free 2-hour course on full Graph Engineering. How to go from one prompt to 100 agents running inside a single graph: 0% → 17:44 - build your first AI agent 25% → 39:30 - run agents with loop engineering 50% → 1:12:38 - turn agent loops into graphs 75% → 1:34:26 - build agents that regulate themselves 100% → 1:55:05 - orchestrate the entire multi-agent system Most people build one agent and stop there. Google is teaching the entire stack: Prompt → Agents → Loops → Graphs → Multi-Agent Systems Single agents are the old workflow. Self-regulating agent graphs are the next one. This 2-hour course is worth more than most paid agent engineering courses. Bookmark it and watch today Then read the full architecture below ↓

Google just released a free 2-hour course on full Graph Engineering. How to go from one prompt to 100 agents running inside a single graph: 0% → 17:44 - build your first AI agent 25% → 39:30 - run agents with loop engineering 50% → 1:12:38 - turn agent loops into graphs 75% → 1:34:26 - build agents that regulate themselves 100% → 1:55:05 - orchestrate the entire multi-agent system Most people build one agent and stop there. Google is teaching the entire stack: Prompt → Agents → Loops → Graphs → Multi-Agent Systems Single agents are the old workflow. Self-regulating agent graphs are the next one. This 2-hour course is worth more than most paid agent engineering courses. Bookmark it and watch today Then read the full architecture below ↓

Lunar

12,020 views • 7 days ago

A 21-YEAR-OLD FROM CHINA RUNS 300 AI AGENTS AT ONCE. THE PART THAT MATTERS ISN'T THE SPEED, IT'S THAT NONE OF THEM CAN LIE TO HIM he opens the dashboard and shows the swarm live, 300 Kimi K2.6 agents firing in parallel, then Opus 4.8 checking every single output against its source. this is not just a faster swarm. it is a loop that refuses to stop while anything is still wrong he pointed it at 100 EV-market companies. first pass: 12 failed. wrong revenue, dead citations, empty fields. second pass: 3 failed. third pass: zero this is not another agent demo. it is a system that catches its own mistakes before he reads a single row

A 21-YEAR-OLD FROM CHINA RUNS 300 AI AGENTS AT ONCE. THE PART THAT MATTERS ISN'T THE SPEED, IT'S THAT NONE OF THEM CAN LIE TO HIM he opens the dashboard and shows the swarm live, 300 Kimi K2.6 agents firing in parallel, then Opus 4.8 checking every single output against its source. this is not just a faster swarm. it is a loop that refuses to stop while anything is still wrong he pointed it at 100 EV-market companies. first pass: 12 failed. wrong revenue, dead citations, empty fields. second pass: 3 failed. third pass: zero this is not another agent demo. it is a system that catches its own mistakes before he reads a single row

NO1ennn

6,953,296 views • 2 months ago

Google just released a free 2-hour course on full Graph Engineering. How to go from one prompt to 100 agents running inside one graph: 17:44 - Build your first AI agent 39:30 - Run agents with loop engineering 1:12:38 - Turn agent loops into graphs 1:34:26 - Build agents that throttle themselves 1:55:05 - Orchestrate the full multi-agent system Most people build one agent and stop there. Google is teaching the full stack: Prompt → Agents → Loops → Graphs → Multi-Agent Systems Single agents are the old workflow. Self-regulating agent graphs are the new one. This 2-hour watch is worth more than most paid agent engineering courses. Bookmark and watch it today Then read the full architecture below ↓

Google just released a free 2-hour course on full Graph Engineering. How to go from one prompt to 100 agents running inside one graph: 17:44 - Build your first AI agent 39:30 - Run agents with loop engineering 1:12:38 - Turn agent loops into graphs 1:34:26 - Build agents that throttle themselves 1:55:05 - Orchestrate the full multi-agent system Most people build one agent and stop there. Google is teaching the full stack: Prompt → Agents → Loops → Graphs → Multi-Agent Systems Single agents are the old workflow. Self-regulating agent graphs are the new one. This 2-hour watch is worth more than most paid agent engineering courses. Bookmark and watch it today Then read the full architecture below ↓

Lunar

401,241 views • 1 month ago

The model sometimes enters a self-critique loop by itself, but you can trigger this manually, and the model tunes the prompt for itself through self-conversation. [Add e.g., "Verify the image, if it's incorrect, write your own prompt, try again, and repeat the process." ]

The model sometimes enters a self-critique loop by itself, but you can trigger this manually, and the model tunes the prompt for itself through self-conversation. [Add e.g., "Verify the image, if it's incorrect, write your own prompt, try again, and repeat the process." ]

Mostafa Dehghani

20,234 views • 1 year ago

There are two types of engineers in 2026 The first opens his laptop in the morning, writes a prompt, waits, reads the diff, fixes it, repeats The second opens his phone, checks what shipped while he was asleep Different answer to one question: who is the loop? The first engineer is the loop, he starts the agent, reviews the output, decides what's next, the moment he steps away it stops The second engineer built the system that is the loop instead of him, PR review, flaky tests, CI triage, all running without him, he just reads the report What stops most people isn't complexity It's that they never noticed they are the bottleneck Full guide to building the system that runs without you below

There are two types of engineers in 2026 The first opens his laptop in the morning, writes a prompt, waits, reads the diff, fixes it, repeats The second opens his phone, checks what shipped while he was asleep Different answer to one question: who is the loop? The first engineer is the loop, he starts the agent, reviews the output, decides what's next, the moment he steps away it stops The second engineer built the system that is the loop instead of him, PR review, flaky tests, CI triage, all running without him, he just reads the report What stops most people isn't complexity It's that they never noticed they are the bottleneck Full guide to building the system that runs without you below

plutos

14,653 views • 2 months ago

Demo 2: human + agent design loop inside Codex. Not every workflow needs the agent to drive everything. You design in Open Design. Codex reviews the output. It can inspect files, open pages, test interactions, critique the design, and turn feedback into the next prompt. Design becomes a human + agent feedback loop.

Demo 2: human + agent design loop inside Codex. Not every workflow needs the agent to drive everything. You design in Open Design. Codex reviews the output. It can inspect files, open pages, test interactions, critique the design, and turn feedback into the next prompt. Design becomes a human + agent feedback loop.

Open Design

20,103 views • 3 months ago