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

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

На главную

the loop is not the whole agent it is only one layer of the system LOOP vs GRAPH vs HARNESS ENGINEERING LOOP ENGINEERING controls iteration turns retries budgets stop conditions success checks stalled progress use durable execution when the run must survive crashes → GRAPH ENGINEERING controls structure nodes...

0xwhrrari's profile picture

rari

9,833 subscribers

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

LIVE

Anya Rossi• Live Now

Private livecam show

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

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

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

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

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

Google just released free 2-hour course on full agent engineering: 1 prompt → agent teams → loops → graphs from 0% to 100%: 10% → 38:46 - build your first agent 30% → 54:46 - connect MCP tools 55% → 1:12:43 - Loop engineering: 4 ways to run agents 70% → 1:20:57 - Graph engineering 100% → 2:22:31 - the full system that works while you sleep most people build one agent and stop there - this is the full path to a system that runs without you from scratch watch it today - then read the full graph engineering playbook below ↓
2:10:34

Google just released free 2-hour course on full agent engineering: 1 prompt → agent teams → loops → graphs from 0% to 100%: 10% → 38:46 - build your first agent 30% → 54:46 - connect MCP tools 55% → 1:12:43 - Loop engineering: 4 ways to run agents 70% → 1:20:57 - Graph engineering 100% → 2:22:31 - the full system that works while you sleep most people build one agent and stop there - this is the full path to a system that runs without you from scratch watch it today - then read the full graph engineering playbook below ↓

codila

525,369 просмотров • 11 дней назад

Google just released free 2-hour course on full Graph engineering: 1 prompt → 100 agents → loops → graphs from 0% to 100%: 10% → 17:44 - build your first agent 30% → 39:30 - Loop engineering: iterate, check, break 60% → 1:12:38 - Graph engineering 75% → 1:34:26 - agents that throttle themselves 100% → 1:55:05 - full graph for multi-agentic systems everyone builds one agent and calls it done - this is the full system where agents wire themselves into a graph watch the course, build the graph - then read the full architecture below ↓
2:03:00

Google just released free 2-hour course on full Graph engineering: 1 prompt → 100 agents → loops → graphs from 0% to 100%: 10% → 17:44 - build your first agent 30% → 39:30 - Loop engineering: iterate, check, break 60% → 1:12:38 - Graph engineering 75% → 1:34:26 - agents that throttle themselves 100% → 1:55:05 - full graph for multi-agentic systems everyone builds one agent and calls it done - this is the full system where agents wire themselves into a graph watch the course, build the graph - then read the full architecture below ↓

codila

457,702 просмотров • 8 дней назад

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 ↓
1:04:49

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

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 ↓
2:05:53

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

386,683 просмотров • 3 дней назад

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

Google just released a free 2-hour+ course on full agent engineering. How to go from one prompt to a system that runs while you sleep: 38:46 - Build your first AI agent 54:46 - Connect MCP tools 1:12:43 - Run agents with four loop patterns 1:20:57 - Turn agent loops into graphs 2:22:31 - Build the complete autonomous system Most people are still building one agent and stopping there. Google is already teaching the full stack: Agents → Tools → Loops → Graphs → Autonomous Systems Single agents are the old workflow. Systems that run without you are the new one. This course is worth more than most paid agent engineering bootcamps. Bookmark and watch it today Then read the full graph engineering playbook below
2:14:04

Google just released a free 2-hour+ course on full agent engineering. How to go from one prompt to a system that runs while you sleep: 38:46 - Build your first AI agent 54:46 - Connect MCP tools 1:12:43 - Run agents with four loop patterns 1:20:57 - Turn agent loops into graphs 2:22:31 - Build the complete autonomous system Most people are still building one agent and stopping there. Google is already teaching the full stack: Agents → Tools → Loops → Graphs → Autonomous Systems Single agents are the old workflow. Systems that run without you are the new one. This course is worth more than most paid agent engineering bootcamps. Bookmark and watch it today Then read the full graph engineering playbook below

Lunar

194,723 просмотров • 11 дней назад

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.
1:43:21

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

194,065 просмотров • 20 дней назад

Anthropic engineer: "You're not supposed to prompt Claude. You're supposed to build a graph that runs itself." In 30 minutes she breaks down how Anthropic builds graphs that remember, learn from their mistakes, and get smarter with every run. The difference between an agent and a graph: one runs once, the other gets better every time. Watch it, then read the full guide on graph engineering below.
31:27

Anthropic engineer: "You're not supposed to prompt Claude. You're supposed to build a graph that runs itself." In 30 minutes she breaks down how Anthropic builds graphs that remember, learn from their mistakes, and get smarter with every run. The difference between an agent and a graph: one runs once, the other gets better every time. Watch it, then read the full guide on graph engineering below.

Mahax

285,553 просмотров • 10 дней назад

You Can Learn AI Agent Harness & Loop Engineering In 19 Min, with LLM Ops, Eval, Tracing and RAG. They went viral not because they're complicated but because they're simple building blocks, and once you see them you can prompt your way to building real systems. 🎬YouTube: Here's the whole thing in one picture. An LLM is a powerful brain that knows everything about humanity and nothing about you or the software you're running. The harness is the set of tools you put on that horse so it runs where you want. Memory gives it context: who you are, what happened before, how to act. The loop lets it call tools again and again, with guardrails so it knows when to stop. Eval and LLM Ops trace every run, score it, and feed the fixes back in so the system keeps improving itself. Master these four and you can read almost any AI agent repo or paper and actually know what's going on. You Can Build Anything. You Can Learn Anything. 💪 Chapters: Intro: the 4 AI agent buzzwords What an AI agent run actually is The memory system: procedural, semantic, episodic What "harness" really means (the horse) Storing and updating memory (databases, skills, summarizer agent) Retrieval: RAG, SQL vs semantic search Tool calling and why agents loop Loop engineering and end-loop guardrails A Claude Code hooks example Eval and LLM Ops: why you need them Tracing every run (Langfuse, LangSmith) Evaluation: LLM as a judge Diagnosing what broke The gate: ship the fix or fix the bug Zoom out: the full system
19:59

You Can Learn AI Agent Harness & Loop Engineering In 19 Min, with LLM Ops, Eval, Tracing and RAG. They went viral not because they're complicated but because they're simple building blocks, and once you see them you can prompt your way to building real systems. 🎬YouTube: Here's the whole thing in one picture. An LLM is a powerful brain that knows everything about humanity and nothing about you or the software you're running. The harness is the set of tools you put on that horse so it runs where you want. Memory gives it context: who you are, what happened before, how to act. The loop lets it call tools again and again, with guardrails so it knows when to stop. Eval and LLM Ops trace every run, score it, and feed the fixes back in so the system keeps improving itself. Master these four and you can read almost any AI agent repo or paper and actually know what's going on. You Can Build Anything. You Can Learn Anything. 💪 Chapters: Intro: the 4 AI agent buzzwords What an AI agent run actually is The memory system: procedural, semantic, episodic What "harness" really means (the horse) Storing and updating memory (databases, skills, summarizer agent) Retrieval: RAG, SQL vs semantic search Tool calling and why agents loop Loop engineering and end-loop guardrails A Claude Code hooks example Eval and LLM Ops: why you need them Tracing every run (Langfuse, LangSmith) Evaluation: LLM as a judge Diagnosing what broke The gate: ship the fix or fix the bug Zoom out: the full system

Shen Sean Chen

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

Head of Claude Code, Boris Cherny: "You're not supposed to write code anymore. You're supposed to build a graph that writes itself." In 30 minutes he breaks down how engineers at Anthropic build graphs that write the code, catch the bugs, and ships. The missing piece most developers skip: how to wire those agents into a graph that runs, verifies, and improves without you. Watch it, then read the full guide on graph engineering below.
31:23

Head of Claude Code, Boris Cherny: "You're not supposed to write code anymore. You're supposed to build a graph that writes itself." In 30 minutes he breaks down how engineers at Anthropic build graphs that write the code, catch the bugs, and ships. The missing piece most developers skip: how to wire those agents into a graph that runs, verifies, and improves without you. Watch it, then read the full guide on graph engineering below.

Mahax

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

context engineering vs graph engineering. every few months the list gets a new word and everyone treats it as a replacement for the last one. these two are not on the same list. one decides what the model sees this turn, the other decides what exists at all. the cleanest way to tell them apart is to ask what a single unit of work looks like. > context engineering is the window the window opens empty, every single time. you assemble what goes in it. the prompt, the docs, the history, the tool results. the assembling is the work. the window only grows. it never shrinks on its own, so eventually something gets dropped. usually from the middle. usually without telling you. then the turn ends and the window is thrown away. not archived, thrown away. the next turn opens empty again and you re-explain what you already explained. good context engineering is knowing what to leave out, not what to pack in. the unit of work is one window. > graph engineering is the structure the same material arrives from the same sources. instead of packing it into a window, you pull entities out of it, resolve the duplicates into one node, and write typed edges between them. nothing here is stored as text you hope to find again. it is stored as a thing with a name and its connections to other things. when the turn ends, the graph is still there. the next turn does not start from zero. it starts by querying what already exists, and the query walks edges instead of guessing at similarity. good graph engineering is deciding what counts as the same thing twice. the unit of work is one relationship. > they are not alternatives the graph is what refills the window. context engineering decides what fits. graph engineering decides what there is to choose from. remove the graph and every session starts blind. remove the context work and the best structure in the world arrives as an unreadable dump. that also tells you which one broke. the answer drifted from what you actually said, or forgot something from this same session. that is the window. the answer is coherent but invents a connection that does not exist, or cannot join two facts it has clearly seen. that is the structure. people debug the prompt because the prompt is the easiest thing to edit. it keeps taking the blame for failures that live a layer down. save this - then read the full breakdown below
0:40

context engineering vs graph engineering. every few months the list gets a new word and everyone treats it as a replacement for the last one. these two are not on the same list. one decides what the model sees this turn, the other decides what exists at all. the cleanest way to tell them apart is to ask what a single unit of work looks like. > context engineering is the window the window opens empty, every single time. you assemble what goes in it. the prompt, the docs, the history, the tool results. the assembling is the work. the window only grows. it never shrinks on its own, so eventually something gets dropped. usually from the middle. usually without telling you. then the turn ends and the window is thrown away. not archived, thrown away. the next turn opens empty again and you re-explain what you already explained. good context engineering is knowing what to leave out, not what to pack in. the unit of work is one window. > graph engineering is the structure the same material arrives from the same sources. instead of packing it into a window, you pull entities out of it, resolve the duplicates into one node, and write typed edges between them. nothing here is stored as text you hope to find again. it is stored as a thing with a name and its connections to other things. when the turn ends, the graph is still there. the next turn does not start from zero. it starts by querying what already exists, and the query walks edges instead of guessing at similarity. good graph engineering is deciding what counts as the same thing twice. the unit of work is one relationship. > they are not alternatives the graph is what refills the window. context engineering decides what fits. graph engineering decides what there is to choose from. remove the graph and every session starts blind. remove the context work and the best structure in the world arrives as an unreadable dump. that also tells you which one broke. the answer drifted from what you actually said, or forgot something from this same session. that is the window. the answer is coherent but invents a connection that does not exist, or cannot join two facts it has clearly seen. that is the structure. people debug the prompt because the prompt is the easiest thing to edit. it keeps taking the blame for failures that live a layer down. save this - then read the full breakdown below

Hanako

19,089 просмотров • 11 дней назад

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
29:10

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,492 просмотров • 1 месяц назад

The founder of LangChain says both models and harnesses have gotten really good between December and now. According to Harrison Chase, the core idea of an agent before Christmas was a model running in a loop and calling tools. This had been the north star for 3 years. - langchain had this when it launched - autogpt was the same idea - openclaw is kind of a future version of it Then about a year ago, they started getting really good. Claude Code, Manus, and Deep Research were all launched around the same time. All of them use the same pattern: running in a loop with harnesses (planning tools, file systems, code execution, etc) Harness engineering became a thing. Then Opus came out in November and really unlocked it. - the harness let the model do more and more - less hardcoded logic - way more control Then everyone went on vacation, played around, and realized that the model and the harness finally worked reliably.
2:10

The founder of LangChain says both models and harnesses have gotten really good between December and now. According to Harrison Chase, the core idea of an agent before Christmas was a model running in a loop and calling tools. This had been the north star for 3 years. - langchain had this when it launched - autogpt was the same idea - openclaw is kind of a future version of it Then about a year ago, they started getting really good. Claude Code, Manus, and Deep Research were all launched around the same time. All of them use the same pattern: running in a loop with harnesses (planning tools, file systems, code execution, etc) Harness engineering became a thing. Then Opus came out in November and really unlocked it. - the harness let the model do more and more - less hardcoded logic - way more control Then everyone went on vacation, played around, and realized that the model and the harness finally worked reliably.

Ivan Burazin

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

Google just released a free 2-hour course on full Graph Engineering. How to go from one prompt to an agent graph that builds itself: 10:16 - Build your first AI agent 41:05 - Master prompt engineering 54:45 - Turn agents into graphs 1:20:10 - Run loops inside agent graphs 1:43:33 - Build a graph that builds itself Most people ship one agent and stop there. Google is teaching everything after: Prompt → Agents → Graphs → Loops → Self-Building Systems Single agents are the old workflow. Graphs that evolve themselves are the new one. This 2-hour watch is worth more than most paid agent engineering courses. Bookmark and watch it today Then read how to run 1,000 agents from one prompt below ↓
1:54:59

Google just released a free 2-hour course on full Graph Engineering. How to go from one prompt to an agent graph that builds itself: 10:16 - Build your first AI agent 41:05 - Master prompt engineering 54:45 - Turn agents into graphs 1:20:10 - Run loops inside agent graphs 1:43:33 - Build a graph that builds itself Most people ship one agent and stop there. Google is teaching everything after: Prompt → Agents → Graphs → Loops → Self-Building Systems Single agents are the old workflow. Graphs that evolve themselves are the new one. This 2-hour watch is worth more than most paid agent engineering courses. Bookmark and watch it today Then read how to run 1,000 agents from one prompt below ↓

Lunar

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

ANTHROPIC'S LEAD ENGINEER SHOWED HOW A LOOP AT $3.10/DAY DOES THE WORK OF A TEAM OF 4 a team of 4 cost $50,000/month - the loop costs $93 and does the same work even better Caching → Routing → Judge → Graph prompt caching cuts input costs by 90% - same prefix hits cache - you pay 10% of the price right model for the right step cuts 60% - easy step goes to Haiku at $0.01, hard step to Fable 5 at $0.15 Opus 5 grades every output at $0.02 per call - one caught mistake pays for a month of judging graph replaces re-asking - known fact goes to graph at $0 - the model never re-infers what the graph already knows save and read below - in 20 minutes your first loop is already running instead of your team
0:45

ANTHROPIC'S LEAD ENGINEER SHOWED HOW A LOOP AT $3.10/DAY DOES THE WORK OF A TEAM OF 4 a team of 4 cost $50,000/month - the loop costs $93 and does the same work even better Caching → Routing → Judge → Graph prompt caching cuts input costs by 90% - same prefix hits cache - you pay 10% of the price right model for the right step cuts 60% - easy step goes to Haiku at $0.01, hard step to Fable 5 at $0.15 Opus 5 grades every output at $0.02 per call - one caught mistake pays for a month of judging graph replaces re-asking - known fact goes to graph at $0 - the model never re-infers what the graph already knows save and read below - in 20 minutes your first loop is already running instead of your team

Noisy

22,369 просмотров • 14 дней назад

This free 2-hour course on "Graph Engineering" gets you Anthropic official "Claude Certified Architect" certificate with it you'll be hired at $250K/year in Anthropic's ecosystem 10% → 22:30 - build your first coordinator agent 30% → 48:18 - agentic loop foundations 45% → 58:14 - teams of agents work while you sleep 70% → 1:14:24 - Loop engineering 100% → 1:41:00 - you are Graph Architect after this 2-hour section - full freeCodeCamp tutorial (12 hours) - go to Anthropic's website and take the exam - you're ready even if you never take the exam - this is still the best graph engineering course I've seen watch it today - then read how to pass this "Claude Certified Architect" exam in the article below ↓
2:16:56

This free 2-hour course on "Graph Engineering" gets you Anthropic official "Claude Certified Architect" certificate with it you'll be hired at $250K/year in Anthropic's ecosystem 10% → 22:30 - build your first coordinator agent 30% → 48:18 - agentic loop foundations 45% → 58:14 - teams of agents work while you sleep 70% → 1:14:24 - Loop engineering 100% → 1:41:00 - you are Graph Architect after this 2-hour section - full freeCodeCamp tutorial (12 hours) - go to Anthropic's website and take the exam - you're ready even if you never take the exam - this is still the best graph engineering course I've seen watch it today - then read how to pass this "Claude Certified Architect" exam in the article below ↓

codila

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

𝗜 𝗼𝗽𝗲𝗻 𝘀𝗼𝘂𝗿𝗰𝗲𝗱 𝗺𝘆 𝗹𝗼𝗰𝗮𝗹 𝗔𝗜 𝗽𝗲𝗿𝘀𝗼𝗻𝗮𝗹 𝗮𝘀𝘀𝗶𝘀𝘁𝗮𝗻𝘁: 𝗔𝗴𝗲𝗻𝘁 𝗛𝗮𝗿𝗻𝗲𝘀𝘀 & 𝗟𝗼𝗼𝗽 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗶𝗻 𝗿𝗲𝗮𝗹 𝗰𝗼𝗱𝗲. Everything in real code you can read in an afternoon: Harness, Loop Engineering, Memory, Eval, Tracing. 100% local on your laptop. 💻 Github Repo: ☕️ Buy me a coffee: The whole system is one loop: message in → retrieval gate → agent run → tools fire → trace → eval → memory saved → skills grow - The loop is ~95 lines of plain Python - Your memory is one SQLite file. Open it. It's yours. - Evals built in: deterministic + LLM-as-judge, with a release gate - Telegram gateway, voice wake word, Apple Calendar tools In the video it books the World Cup QF on my calendar, remembers who my friends are, and answers me on Telegram. Clone it, star it, break it, PR it. Repo + 20-min walkthrough in the first reply 👇 Watch it, then save the architecture diagram below. 🔖 You Can Build Anything. You Can Learn Anything. 💪
20:48

𝗜 𝗼𝗽𝗲𝗻 𝘀𝗼𝘂𝗿𝗰𝗲𝗱 𝗺𝘆 𝗹𝗼𝗰𝗮𝗹 𝗔𝗜 𝗽𝗲𝗿𝘀𝗼𝗻𝗮𝗹 𝗮𝘀𝘀𝗶𝘀𝘁𝗮𝗻𝘁: 𝗔𝗴𝗲𝗻𝘁 𝗛𝗮𝗿𝗻𝗲𝘀𝘀 & 𝗟𝗼𝗼𝗽 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗶𝗻 𝗿𝗲𝗮𝗹 𝗰𝗼𝗱𝗲. Everything in real code you can read in an afternoon: Harness, Loop Engineering, Memory, Eval, Tracing. 100% local on your laptop. 💻 Github Repo: ☕️ Buy me a coffee: The whole system is one loop: message in → retrieval gate → agent run → tools fire → trace → eval → memory saved → skills grow - The loop is ~95 lines of plain Python - Your memory is one SQLite file. Open it. It's yours. - Evals built in: deterministic + LLM-as-judge, with a release gate - Telegram gateway, voice wake word, Apple Calendar tools In the video it books the World Cup QF on my calendar, remembers who my friends are, and answers me on Telegram. Clone it, star it, break it, PR it. Repo + 20-min walkthrough in the first reply 👇 Watch it, then save the architecture diagram below. 🔖 You Can Build Anything. You Can Learn Anything. 💪

Shen Sean Chen

34,182 просмотров • 26 дней назад

Free 3-hour course from an ex-Google engineer. AI agents, graph engineering, harness, agent loops. Covers more than most $500 paid courses. This is the exact playbook to learn how to actually build and monetize AI agents. Don't miss your shot, save it now. • 0:00 - Design an AI agent system from scratch • 7:38 - When your agent should hand off to a human • 19:27 - RAG and vector databases explained simply • 52:38 - Deploy your AI agent to Google Cloud • 1:25:57 - Turn AI agents into a paid business via WhatsApp • 1:33:00 - Turn conversations into real leads automatically • 2:24:01 - Loop engineering vs graphs, the real difference • 2:33:08 - Build your own multi-tool agent graph Save this video, because it's the only one that can actually take you to your $2,000+ profit.
2:45:36

Free 3-hour course from an ex-Google engineer. AI agents, graph engineering, harness, agent loops. Covers more than most $500 paid courses. This is the exact playbook to learn how to actually build and monetize AI agents. Don't miss your shot, save it now. • 0:00 - Design an AI agent system from scratch • 7:38 - When your agent should hand off to a human • 19:27 - RAG and vector databases explained simply • 52:38 - Deploy your AI agent to Google Cloud • 1:25:57 - Turn AI agents into a paid business via WhatsApp • 1:33:00 - Turn conversations into real leads automatically • 2:24:01 - Loop engineering vs graphs, the real difference • 2:33:08 - Build your own multi-tool agent graph Save this video, because it's the only one that can actually take you to your $2,000+ profit.

unicode

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

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