Загрузка видео...

Не удалось загрузить видео

Возникла проблема при загрузке этого видео. Это может быть связано с временными проблемами сети или видео может быть недоступно.

На главную

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

codila

8,828 subscribers

23,915 просмотров • 6 дней назад •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

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

94,492 просмотров • 5 дней назад

Godfather of agents showed how he created the loop engineering that everyone now uses: as PhD student, he wrote the formula every AI agent now runs on - his formula taught agents to self-improve here's the formula: step 1 → stop making the model just think OR just act - make it alternate: think → act → observe → think again step 2 → let it reason out loud before every action - the plan guides the next move, not just the output step 3 → feed the result of each action back in - the model reads what happened and adjusts, live step 4 → when it fails, don't restart make it reflect on WHY it failed, in words, then retry with that memory step 5 → store those reflections - the agent gets better across attempts without any retraining before OpenAI, before he ran Tencent's AI - he was a grad student who quietly wrote the blueprint every agent now follows - now give 90-min course watch & bookmark - then read how the agent systems actually works ↓

Godfather of agents showed how he created the loop engineering that everyone now uses: as PhD student, he wrote the formula every AI agent now runs on - his formula taught agents to self-improve here's the formula: step 1 → stop making the model just think OR just act - make it alternate: think → act → observe → think again step 2 → let it reason out loud before every action - the plan guides the next move, not just the output step 3 → feed the result of each action back in - the model reads what happened and adjusts, live step 4 → when it fails, don't restart make it reflect on WHY it failed, in words, then retry with that memory step 5 → store those reflections - the agent gets better across attempts without any retraining before OpenAI, before he ran Tencent's AI - he was a grad student who quietly wrote the blueprint every agent now follows - now give 90-min course watch & bookmark - then read how the agent systems actually works ↓

codila

28,359 просмотров • 9 дней назад

Ex-Google engineer explained AI agent loops, harness, evals in 20 minutes - better than 500$ courses. trace every run → judge it with an LLM → diagnose → fix → ship. That loop is how agents self-improve over time. Agent loops + memory + harness + evals - thats the stack. Watch it, then save the framework below.

Ex-Google engineer explained AI agent loops, harness, evals in 20 minutes - better than 500$ courses. trace every run → judge it with an LLM → diagnose → fix → ship. That loop is how agents self-improve over time. Agent loops + memory + harness + evals - thats the stack. Watch it, then save the framework below.

Movez

558,737 просмотров • 29 дней назад

"The model is no longer the product. Codex, Perplexity Computer, or Claude Code - all are orchestration system. It takes a model and pairs it with an agent harness. What is an agent harness ? The rules for how the agent loops around" - Aravind Srinivas

"The model is no longer the product. Codex, Perplexity Computer, or Claude Code - all are orchestration system. It takes a model and pairs it with an agent harness. What is an agent harness ? The rules for how the agent loops around" - Aravind Srinivas

Rohan Paul

119,783 просмотров • 1 месяц назад

$FET just quietly built the internet for AI agents. 3,000,000 agents. One network. One token. Here's what nobody is explaining: Every AI agent needs 3 things to be useful: An address. A way to be found. A way to get paid. Agentverse gives agents all three. Your agent becomes discoverable on ASI: One. Other agents can find it, call it, or hire it. Automatically. No human in the loop. This is agent-to-agent commerce. And every transaction settles in $FET. More agents = more activity = more demand. The infrastructure is already live. The economy is just getting started.

$FET just quietly built the internet for AI agents. 3,000,000 agents. One network. One token. Here's what nobody is explaining: Every AI agent needs 3 things to be useful: An address. A way to be found. A way to get paid. Agentverse gives agents all three. Your agent becomes discoverable on ASI: One. Other agents can find it, call it, or hire it. Automatically. No human in the loop. This is agent-to-agent commerce. And every transaction settles in $FET. More agents = more activity = more demand. The infrastructure is already live. The economy is just getting started.

2xnmore

12,894 просмотров • 3 месяцев назад

Anthropic engineer just released a 2-hour workshop on "Graph Engineering" for agentic systems: “80% of our engineers are using self-improving loops. Now everyone is building agentic graphs.” • 00:00 - Introduction to RAG & Graphs • 06:39 - Core of "Graph Engineering" (state, nodes) • 14:29 - 3 feedback loops of Graph agents • 23:06 - Agent evaluation with Graphs • 36:29 - Agent cycles in graphs • 1:15:22 - Agentic RAG & agent context • 1:41:20 - Evaluation datasets based on Graphs This 2-hour workshop will replace 10 paid courses on agentic engineering. Watch it today, then learn how to become a Graph Engineer in the article below.

Anthropic engineer just released a 2-hour workshop on "Graph Engineering" for agentic systems: “80% of our engineers are using self-improving loops. Now everyone is building agentic graphs.” • 00:00 - Introduction to RAG & Graphs • 06:39 - Core of "Graph Engineering" (state, nodes) • 14:29 - 3 feedback loops of Graph agents • 23:06 - Agent evaluation with Graphs • 36:29 - Agent cycles in graphs • 1:15:22 - Agentic RAG & agent context • 1:41:20 - Evaluation datasets based on Graphs This 2-hour workshop will replace 10 paid courses on agentic engineering. Watch it today, then learn how to become a Graph Engineer in the article below.

Codez

363,836 просмотров • 2 дней назад

Andrew Ng built agentic knowledge graph that runs agents loops from scratch: his agents searched thousands of tools through the graph, found the "right" one by meaning, and called it agent efficiency increased by 90% here's how: step 1 → embed every tool, search by meaning - not just keywords step 2 → but "similar" ≠ "correct" - it grabs the wrong one, skips the step before it step 3 → map tools as a graph - nodes are tools, edges are what runs before what step 4 → retrieve the path, not one tool - every tool the task needs, in order step 5 → bake the process into the graph - the sequence becomes data, not a guess most agents fail here and no one knows why - 1-hour brilliant course about it watch & bookmark - then read full course about graph engineering ↓

Andrew Ng built agentic knowledge graph that runs agents loops from scratch: his agents searched thousands of tools through the graph, found the "right" one by meaning, and called it agent efficiency increased by 90% here's how: step 1 → embed every tool, search by meaning - not just keywords step 2 → but "similar" ≠ "correct" - it grabs the wrong one, skips the step before it step 3 → map tools as a graph - nodes are tools, edges are what runs before what step 4 → retrieve the path, not one tool - every tool the task needs, in order step 5 → bake the process into the graph - the sequence becomes data, not a guess most agents fail here and no one knows why - 1-hour brilliant course about it watch & bookmark - then read full course about graph engineering ↓

codila

16,276 просмотров • 6 дней назад

ex-Anthropic engineer: "I left Anthropic to build agents systems in Google but nothing beats Claude as an agent yet - in coding and tool use, the rest are still behind " in this 90-min podcast, he showed how to build effective agent system with Claude from scratch to get into Anthropic, he hand-coded Karpathy's nanoGPT as a physicist Claude → tools → loops of verification → a real agent and why, at Google, he says Claude is the best watch & bookmark - then read the guide to agent systems ↓

ex-Anthropic engineer: "I left Anthropic to build agents systems in Google but nothing beats Claude as an agent yet - in coding and tool use, the rest are still behind " in this 90-min podcast, he showed how to build effective agent system with Claude from scratch to get into Anthropic, he hand-coded Karpathy's nanoGPT as a physicist Claude → tools → loops of verification → a real agent and why, at Google, he says Claude is the best watch & bookmark - then read the guide to agent systems ↓

codila

125,694 просмотров • 7 дней назад

Anthropic Managed Agents team: "Fable 5 is our best model for running self-improving agent systems. Add /loops, dynamic workflows, dreaming and you are unstoppable" in this video he breaks down exactly how most people are using Claude: - the 34% you lose to CLAUDE.md before typing a word - one agent researching. one building. one reviewing. one orchestrating - the architecture that separates hobbyists from real builders - the 3 properties every agent team needs to actually survive if you've been using Claude for more than a month and never left the chat window, you've been using one agent when you could be running a team of them instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed the guide is in the article below

Anthropic Managed Agents team: "Fable 5 is our best model for running self-improving agent systems. Add /loops, dynamic workflows, dreaming and you are unstoppable" in this video he breaks down exactly how most people are using Claude: - the 34% you lose to CLAUDE.md before typing a word - one agent researching. one building. one reviewing. one orchestrating - the architecture that separates hobbyists from real builders - the 3 properties every agent team needs to actually survive if you've been using Claude for more than a month and never left the chat window, you've been using one agent when you could be running a team of them instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed the guide is in the article below

Khairallah AL-Awady

21,533 просмотров • 1 месяц назад

HERMES AGENT IS THE MOST POWERFUL OPEN SOURCE AI AGENT FRAMEWORK AVAILABLE RIGHT NOW — AND MOST PEOPLE HAVE NO IDEA HOW TO USE IT PROPERLY. This masterclass fixes that completely. From zero to a fully operational autonomous agent system in one sitting. Installation. Skills. Memory. MCP servers. Scheduler. Multi-agent operations. Every section builds on the previous one. The people who read this this weekend will have a production-ready autonomous agent operation running by Monday. Read this and bookmark it now.

HERMES AGENT IS THE MOST POWERFUL OPEN SOURCE AI AGENT FRAMEWORK AVAILABLE RIGHT NOW — AND MOST PEOPLE HAVE NO IDEA HOW TO USE IT PROPERLY. This masterclass fixes that completely. From zero to a fully operational autonomous agent system in one sitting. Installation. Skills. Memory. MCP servers. Scheduler. Multi-agent operations. Every section builds on the previous one. The people who read this this weekend will have a production-ready autonomous agent operation running by Monday. Read this and bookmark it now.

CyrilXBT

34,120 просмотров • 1 месяц назад

Google senior engineer just dropped a free 8-minute lesson on building AI agentic systems. This is the clearest explanation of multi-agent AI systems and loops you'll find on the internet. People still paying 500$ for agentic courses, while Google makes it for free. Agent Studio → Loops → Managed Agents → Antigravity → ADK 2.0 - thats the stack Watch it, then read the full guide on loop engineering below.

Google senior engineer just dropped a free 8-minute lesson on building AI agentic systems. This is the clearest explanation of multi-agent AI systems and loops you'll find on the internet. People still paying 500$ for agentic courses, while Google makes it for free. Agent Studio → Loops → Managed Agents → Antigravity → ADK 2.0 - thats the stack Watch it, then read the full guide on loop engineering below.

Codez

32,021 просмотров • 1 месяц назад

Anthropic engineer: "Stop re-prompting Claude all day. Build the loop once. Let it do the work." 00:00 - Build your first autonomous agent 05:02 - Make the loop fix its own mistakes 16:43 - Give Claude memory across sessions Prompting is the old workflow. Loops are the new one. This 30-minute watch is worth more than most paid agent courses. Bookmark and watch it today Then read the step-by-step guide below

Anthropic engineer: "Stop re-prompting Claude all day. Build the loop once. Let it do the work." 00:00 - Build your first autonomous agent 05:02 - Make the loop fix its own mistakes 16:43 - Give Claude memory across sessions Prompting is the old workflow. Loops are the new one. This 30-minute watch is worth more than most paid agent courses. Bookmark and watch it today Then read the step-by-step guide below

Lunar

312,521 просмотров • 6 дней назад

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,379 просмотров • 22 дней назад

Google just released a 1-hour course on building agentic knowledge Graphs from scratch: • 00:00 - Introduction to AI agents • 08:09 - Foundations of multi-agent systems • 13:25 - Introduction to Graph engineering • 23:27 - Environment setup for agentic Graphs • 47:43 - Building Graph RAG agents • 1:25:14 - Agent memory bank with graphs Worth more than 10 articles on loop engineering. Watch it today, then read how to become a graph engineer in the article below.

Google just released a 1-hour course on building agentic knowledge Graphs from scratch: • 00:00 - Introduction to AI agents • 08:09 - Foundations of multi-agent systems • 13:25 - Introduction to Graph engineering • 23:27 - Environment setup for agentic Graphs • 47:43 - Building Graph RAG agents • 1:25:14 - Agent memory bank with graphs Worth more than 10 articles on loop engineering. Watch it today, then read how to become a graph engineer in the article below.

Codez

190,524 просмотров • 6 дней назад

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

176,175 просмотров • 1 месяц назад

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.

Jurij Skornik

11,070 просмотров • 2 месяцев назад

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

Yarchi

58,186 просмотров • 1 месяц назад

The Model Context Protocol (MCP) is powerful, but it's not enough. In the age of AI agents you absolutely need a COORDINATION LAYER that makes agent-to-agent / agent-to-system interactions reliable, composable, and rule-bound. That's Sui.

The Model Context Protocol (MCP) is powerful, but it's not enough. In the age of AI agents you absolutely need a COORDINATION LAYER that makes agent-to-agent / agent-to-system interactions reliable, composable, and rule-bound. That's Sui.

Adeniyi.sui

24,521 просмотров • 1 год назад

The creator of Pydantic explained how to make live agents smarter after they ship in 1 hour 21 minutes - better than $2500 agent evals bootcamps. collect traces from your live agent -> score them with an eval -> run GEPA to auto-optimize the prompt -> deploy the winner -> repeat forever. That loop is how Pydantic AI agents self-improve while running in production. Pydantic AI + Logfire tracing + GEPA prompt optimizer + evals + feedback loops - that's the stack. Watch and save it, then wire GEPA into your live agent this week.

The creator of Pydantic explained how to make live agents smarter after they ship in 1 hour 21 minutes - better than $2500 agent evals bootcamps. collect traces from your live agent -> score them with an eval -> run GEPA to auto-optimize the prompt -> deploy the winner -> repeat forever. That loop is how Pydantic AI agents self-improve while running in production. Pydantic AI + Logfire tracing + GEPA prompt optimizer + evals + feedback loops - that's the stack. Watch and save it, then wire GEPA into your live agent this week.

h100envy

49,466 просмотров • 9 дней назад

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.

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

218,959 просмотров • 1 месяц назад