Loading video...

Video Failed to Load

Go Home

This 1-min clip from the creator of LangChain + this 10-min read from him will teach you more about what actually matters in AI agents than everything you've scrolled past this year. Watch this. Then read below. You'll think about agents differently after. -Memory defines how an agent behaves;...

Av1dlive's profile picture

Avid

10,602 subscribers

16,898 views • 5 months ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

This 15-minute talk by the creator of Pydantic on how to correctly use MCPs will teach you more about making your AI tools actually work together than everything you've scrolled past this year. Bookmark this & watch, no matter what. Then read the guide below by Khairallah AL-Awady
15:09

This 15-minute talk by the creator of Pydantic on how to correctly use MCPs will teach you more about making your AI tools actually work together than everything you've scrolled past this year. Bookmark this & watch, no matter what. Then read the guide below by Khairallah AL-Awady

Avid

371,321 views • 5 months ago

This 25-minute talk by Anthropic's own applied AI team on how to use MCPs correctly teach you more about making your AI tools actually work together than everything you've scrolled past this year. Bookmark this & watch, no matter what. Then read the guide below.
25:58

This 25-minute talk by Anthropic's own applied AI team on how to use MCPs correctly teach you more about making your AI tools actually work together than everything you've scrolled past this year. Bookmark this & watch, no matter what. Then read the guide below.

Khairallah AL-Awady

66,688 views • 5 months ago

New course: Agent Memory: Building Memory-Aware Agents, built in partnership with Oracle and taught by Richmond Alake and Nacho Martínez. Many agents work well within a single session but their memory resets once the session ends. Consider a research agent working on dozens of papers across multiple days: without memory, it has no way to store and retrieve what it learned across sessions. This short course teaches you to build a memory system that enables agents to persist memory and thereby learn across sessions. You'll design a Memory Manager that handles different memory types, implement semantic tool retrieval that scales without bloating the context, and build write-back pipelines that let your agent autonomously update and refine what it knows over time. Skills you'll gain: - Build persistent memory stores for different agent memory types - Implement a Memory Manager that orchestrates how your agent reads, writes, and retrieves memory - Treat tools as procedural memory and retrieve only relevant ones at inference time using semantic search Join and learn to build agents that remember and improve over time!
1:37

New course: Agent Memory: Building Memory-Aware Agents, built in partnership with Oracle and taught by Richmond Alake and Nacho Martínez. Many agents work well within a single session but their memory resets once the session ends. Consider a research agent working on dozens of papers across multiple days: without memory, it has no way to store and retrieve what it learned across sessions. This short course teaches you to build a memory system that enables agents to persist memory and thereby learn across sessions. You'll design a Memory Manager that handles different memory types, implement semantic tool retrieval that scales without bloating the context, and build write-back pipelines that let your agent autonomously update and refine what it knows over time. Skills you'll gain: - Build persistent memory stores for different agent memory types - Implement a Memory Manager that orchestrates how your agent reads, writes, and retrieves memory - Treat tools as procedural memory and retrieve only relevant ones at inference time using semantic search Join and learn to build agents that remember and improve over time!

Andrew Ng

161,260 views • 6 months ago

ANTHROPIC KILLED THE VECTOR DATABASE AND REPLACED IT WITH A FOLDER no embeddings. no black-box retrieval. no special memory tools. the agent just reads and writes a folder the insight: your agent already knows how to use a filesystem. so Anthropic made long-term memory a directory of small markdown files, mounted straight into the agent's sandbox at /mnt/memory the agent manages it with the tools it already has, bash, read, write, edit, grep, and Anthropic auto-injects a note into the system prompt so the agent always knows the memory is there and where to look the result: > every change is an immutable version: full audit trail, point-in-time recovery, redaction > read-only or read-write per store, so many agents can safely share one memory > workspace-scoped and persistent, memory that survives every session end most teams bolt on a vector DB and pray retrieval works. Anthropic went the opposite way: compiled knowledge as plain, human-readable files you can open, diff, and edit yourself and there's a second layer. Anthropic's "Dreaming" runs offline, reviews past sessions and the store, and rewrites it into a cleaner, higher-signal version. the agent literally consolidates memory in its sleep. bookmark this. the most production-grade agent memory right now is just a well-organized folder, and Anthropic proved it.
0:50

ANTHROPIC KILLED THE VECTOR DATABASE AND REPLACED IT WITH A FOLDER no embeddings. no black-box retrieval. no special memory tools. the agent just reads and writes a folder the insight: your agent already knows how to use a filesystem. so Anthropic made long-term memory a directory of small markdown files, mounted straight into the agent's sandbox at /mnt/memory the agent manages it with the tools it already has, bash, read, write, edit, grep, and Anthropic auto-injects a note into the system prompt so the agent always knows the memory is there and where to look the result: > every change is an immutable version: full audit trail, point-in-time recovery, redaction > read-only or read-write per store, so many agents can safely share one memory > workspace-scoped and persistent, memory that survives every session end most teams bolt on a vector DB and pray retrieval works. Anthropic went the opposite way: compiled knowledge as plain, human-readable files you can open, diff, and edit yourself and there's a second layer. Anthropic's "Dreaming" runs offline, reviews past sessions and the store, and rewrites it into a cleaner, higher-signal version. the agent literally consolidates memory in its sleep. bookmark this. the most production-grade agent memory right now is just a well-organized folder, and Anthropic proved it.

NO1ennn

13,359 views • 1 month ago

This 1 hour MIT lecture about "Machine Learning" will tell you more about how to build your own ML model than 2 months of internship at OpenAI. Bookmark this & give it 1 hour today, no matter what. This will change the way you use AI. Then read the post below.
50:58

This 1 hour MIT lecture about "Machine Learning" will tell you more about how to build your own ML model than 2 months of internship at OpenAI. Bookmark this & give it 1 hour today, no matter what. This will change the way you use AI. Then read the post below.

Movez

84,433 views • 5 months ago

Anthropic's Head of Product just dropped a 28-minute masterclass on agent production. Prompt caching. Tool search. Programmatic tool calling. Compaction. Advisor strategy. 28 minutes. Free. Worth more than 100 YouTube videos combined. Watch it first. Then read this. The masterclass teaches you how agents work. This teaches you what to build with them — a 5-agent content pipeline that does the work of a $300K creative team. Full pipeline below ↓ Bookmark this. Start this weekend.
27:13

Anthropic's Head of Product just dropped a 28-minute masterclass on agent production. Prompt caching. Tool search. Programmatic tool calling. Compaction. Advisor strategy. 28 minutes. Free. Worth more than 100 YouTube videos combined. Watch it first. Then read this. The masterclass teaches you how agents work. This teaches you what to build with them — a 5-agent content pipeline that does the work of a $300K creative team. Full pipeline below ↓ Bookmark this. Start this weekend.

Rahul

534,327 views • 4 months ago

ANTHROPIC ENGINEER JUST LANDED A HUGE INVESTMENT FOR A MEMORY SYSTEM THAT NEVER FORGETS Most agents wake up blank every session, forgetting everything the moment the conversation ends. He built a scoring layer instead, one that decides what actually matters past this session and what gets dropped. Contradictions between old and new memory get flagged automatically, never silently overwritten the way most systems do. Memory that never gets touched again quietly decays on its own, so nothing bloats the system with dead weight. Nobody outside the deal knew what the scoring layer actually did before the check cleared. See how the scoring layer actually decides what survives below👇
0:20

ANTHROPIC ENGINEER JUST LANDED A HUGE INVESTMENT FOR A MEMORY SYSTEM THAT NEVER FORGETS Most agents wake up blank every session, forgetting everything the moment the conversation ends. He built a scoring layer instead, one that decides what actually matters past this session and what gets dropped. Contradictions between old and new memory get flagged automatically, never silently overwritten the way most systems do. Memory that never gets touched again quietly decays on its own, so nothing bloats the system with dead weight. Nobody outside the deal knew what the scoring layer actually did before the check cleared. See how the scoring layer actually decides what survives below👇

wast3

74,869 views • 1 month ago

Hermes Desktop just removed the biggest barrier to AI agents. No more terminal. Here’s what changed everything: → You can now run Hermes in a clean Mac app → Edit memory + skills without SSH → Search every past conversation instantly → Run multi-agent workflows visually → Assign tasks like a real team board This turns AI from “tool” → “operator.” Save this video, you’ll finally understand how agents actually work. Want the SOP? DM me. 💬
9:16

Hermes Desktop just removed the biggest barrier to AI agents. No more terminal. Here’s what changed everything: → You can now run Hermes in a clean Mac app → Edit memory + skills without SSH → Search every past conversation instantly → Run multi-agent workflows visually → Assign tasks like a real team board This turns AI from “tool” → “operator.” Save this video, you’ll finally understand how agents actually work. Want the SOP? DM me. 💬

Julian Goldie SEO

43,421 views • 4 months ago

Anthropic engineer: "You don't need better prompts. You need graph engineering: memory that stays, so your agent never forgets anything." In 28 minutes he shows what Anthropic does differently, how to build and structure work with agents. This beats any paid agent course I've seen. Watch it, then read the graph engineering guide below 👇
28:26

Anthropic engineer: "You don't need better prompts. You need graph engineering: memory that stays, so your agent never forgets anything." In 28 minutes he shows what Anthropic does differently, how to build and structure work with agents. This beats any paid agent course I've seen. Watch it, then read the graph engineering guide below 👇

darkzodchi

463,650 views • 1 month ago

A FORMER GOOGLE LEAD BUILT A MEMORY SYSTEM THAT NEVER LOSES A SINGLE DETAIL Most agents forget everything the moment a session ends, starting from zero every single time. He built a scoring layer instead, one that decides what actually matters past this session and what gets dropped. Contradictions between old and new memory get flagged automatically, never silently overwritten the way most systems do. Memory that never gets touched again quietly decays on its own, so nothing bloats the system with dead weight. He left one of the biggest labs in the world to build the thing they said couldn't be solved yet. See how the scoring layer actually decides what survives below👇
0:20

A FORMER GOOGLE LEAD BUILT A MEMORY SYSTEM THAT NEVER LOSES A SINGLE DETAIL Most agents forget everything the moment a session ends, starting from zero every single time. He built a scoring layer instead, one that decides what actually matters past this session and what gets dropped. Contradictions between old and new memory get flagged automatically, never silently overwritten the way most systems do. Memory that never gets touched again quietly decays on its own, so nothing bloats the system with dead weight. He left one of the biggest labs in the world to build the thing they said couldn't be solved yet. See how the scoring layer actually decides what survives below👇

wast3

26,649 views • 1 month ago

New short course: LLMs as Operating Systems: Agent Memory, created with Letta, and taught by its founders Charles Packer and Sarah Wooders. An LLM's input context window has limited space. Using a longer input context also costs more and results in slower processing. So, managing what's stored in this context window is important. In the innovative paper MemGPT: Towards LLMs as Operating Systems, its authors (which include the instructors) proposed using an LLM agent to manage this context window. Their system uses a large persistent memory that stores everything that could be included in the input context, and an agent decides what is actually included. Take the example of building a chatbot that needs to remember what's been said earlier in a conversation (perhaps over many days of interaction with a user). As the conversation's length grows, the memory management agent will move information from the input context to a persistent searchable database; summarize information to keep relevant facts in the input context; and restore relevant conversation elements from further back in time. This allows a chatbot to keep what's currently most relevant in its input context memory to generate the next response. When I read the original MemGPT paper, I thought it was an innovative technique for handling memory for LLMs. The open-source Letta framework, which we'll use in this course, makes MemGPT easy to implement. It adds memory to your LLM agents and gives them transparent long-term memory. In detail, you’ll learn: - How to build an agent that can edit its own limited input context memory, using tools and multi-step reasoning - What is a memory hierarchy (an idea from computer operating systems, which use a cache to speed up memory access), and how these ideas apply to managing the LLM input context (where the input context window is a "cache" storing the most relevant information; and an agent decides what to move in and out of this to/from a larger persistent storage system) - How to implement multi-agent collaboration by letting different agents share blocks of memory This course will give you a sophisticated understanding of memory management for LLMs, which is important for chatbots having long conversations, and for complex agentic workflows. Please sign up here!
2:57

New short course: LLMs as Operating Systems: Agent Memory, created with Letta, and taught by its founders Charles Packer and Sarah Wooders. An LLM's input context window has limited space. Using a longer input context also costs more and results in slower processing. So, managing what's stored in this context window is important. In the innovative paper MemGPT: Towards LLMs as Operating Systems, its authors (which include the instructors) proposed using an LLM agent to manage this context window. Their system uses a large persistent memory that stores everything that could be included in the input context, and an agent decides what is actually included. Take the example of building a chatbot that needs to remember what's been said earlier in a conversation (perhaps over many days of interaction with a user). As the conversation's length grows, the memory management agent will move information from the input context to a persistent searchable database; summarize information to keep relevant facts in the input context; and restore relevant conversation elements from further back in time. This allows a chatbot to keep what's currently most relevant in its input context memory to generate the next response. When I read the original MemGPT paper, I thought it was an innovative technique for handling memory for LLMs. The open-source Letta framework, which we'll use in this course, makes MemGPT easy to implement. It adds memory to your LLM agents and gives them transparent long-term memory. In detail, you’ll learn: - How to build an agent that can edit its own limited input context memory, using tools and multi-step reasoning - What is a memory hierarchy (an idea from computer operating systems, which use a cache to speed up memory access), and how these ideas apply to managing the LLM input context (where the input context window is a "cache" storing the most relevant information; and an agent decides what to move in and out of this to/from a larger persistent storage system) - How to implement multi-agent collaboration by letting different agents share blocks of memory This course will give you a sophisticated understanding of memory management for LLMs, which is important for chatbots having long conversations, and for complex agentic workflows. Please sign up here!

Andrew Ng

201,127 views • 1 year ago

holy sh*t. this is f**king insane. langchain just documented the missing memory layer for agents that are supposed to improve after every run. instead of stuffing everything into one giant prompt, deep agents can keep long-term memory, reusable skills and lessons from previous tasks. [it takes a few minutes to understand the loop] 1/ run the task 2/ save what actually worked 3/ load that lesson into the next run that’s how an agent stops starting from zero every single time.
0:21

holy sh*t. this is f**king insane. langchain just documented the missing memory layer for agents that are supposed to improve after every run. instead of stuffing everything into one giant prompt, deep agents can keep long-term memory, reusable skills and lessons from previous tasks. [it takes a few minutes to understand the loop] 1/ run the task 2/ save what actually worked 3/ load that lesson into the next run that’s how an agent stops starting from zero every single time.

Gipp 🦅

33,406 views • 14 days ago

Your OpenClaw🦞 agent works perfectly for 20 minutes. Then it silently forgets your instructions and goes rogue. The fix isn't better prompts. It's understanding how memory actually works. I'm an OpenClaw maintainer. After 2+ months of daily use, I ended up with a memory system where my agent remembers decisions from weeks ago, checks its notes before acting, and picks up exactly where it left off after every restart: 0:00 The real reason your agent forgets 1:59 Quick start: 3 things that matter most 3:01 The 4 "memories" people confuse 4:52 3 failure modes: why your agent forgets 6:42 Compaction vs pruning 8:05 Prove what's loaded: /context list 10:06 What compaction actually does 13:42 Layer 1: pre-compaction memory flush 16:27 Layer 2: manual saves + /compact trick 19:12 Layer 3: the file architecture 23:22 The memory protocol for AGENTS.md 26:06 Retrieval: Track A, A+, and QMD by tobi lutke 31:59 Cost and cache 33:33 The complete config (copy and go) 36:35 5 things to remember
37:33

Your OpenClaw🦞 agent works perfectly for 20 minutes. Then it silently forgets your instructions and goes rogue. The fix isn't better prompts. It's understanding how memory actually works. I'm an OpenClaw maintainer. After 2+ months of daily use, I ended up with a memory system where my agent remembers decisions from weeks ago, checks its notes before acting, and picks up exactly where it left off after every restart: 0:00 The real reason your agent forgets 1:59 Quick start: 3 things that matter most 3:01 The 4 "memories" people confuse 4:52 3 failure modes: why your agent forgets 6:42 Compaction vs pruning 8:05 Prove what's loaded: /context list 10:06 What compaction actually does 13:42 Layer 1: pre-compaction memory flush 16:27 Layer 2: manual saves + /compact trick 19:12 Layer 3: the file architecture 23:22 The memory protocol for AGENTS.md 26:06 Retrieval: Track A, A+, and QMD by tobi lutke 31:59 Cost and cache 33:33 The complete config (copy and go) 36:35 5 things to remember

Radek Sienkiewicz

94,880 views • 6 months ago

The reason your AI gives generic answers isn't the model. It's that your company's knowledge lives in 12 different tools and your agent can't see any of it. So here's how to build a context database your agents can actually use: 1) Pull it in: - Slack, email, meetings, docs, tickets - Auto-collected on a schedule into one place. 2) Clean it up. - An agent files what matters and drops the noise, so your brain doesn't bloat. 3) Store it as memory. - Folders of files your agents read from and write back to as they learn. 4) Point your agents at it. - Now they draft, build, and ship with full context instead of guessing. Same model. Same agent. The difference is whether it can understand your company or not. Build the database once. Everything downstream gets smarter.
8:17

The reason your AI gives generic answers isn't the model. It's that your company's knowledge lives in 12 different tools and your agent can't see any of it. So here's how to build a context database your agents can actually use: 1) Pull it in: - Slack, email, meetings, docs, tickets - Auto-collected on a schedule into one place. 2) Clean it up. - An agent files what matters and drops the noise, so your brain doesn't bloat. 3) Store it as memory. - Folders of files your agents read from and write back to as they learn. 4) Point your agents at it. - Now they draft, build, and ship with full context instead of guessing. Same model. Same agent. The difference is whether it can understand your company or not. Build the database once. Everything downstream gets smarter.

The Startup Ideas Podcast (SIP) 🧃

13,666 views • 3 months ago

✨New LangChain Academy Course: Learn to build with LangSmith Agent Builder 🪄 Learn how to build your own agents with LangSmith Agent Builder. Anyone can now build agents for complex daily tasks, without writing code. We built Agent Builder for anyone whose day gets swallowed by routine work. The research, follow-ups, updates, scheduling, and status checks that are essential to your operations, but quickly take over your calendar. Agent Builder is different from traditional workflow automations. You don’t need to map every step, tinker with if-this-then-that branching, or babysit dependencies. You just give it feedback like you would a teammate, and the agent learns using its memory. In this quickstart course, you'll learn how to: - Build an email agent - Understand what agents can do - Improve your agent - Set up triggers and your Agent Inbox Enroll for free ➡️
1:45

✨New LangChain Academy Course: Learn to build with LangSmith Agent Builder 🪄 Learn how to build your own agents with LangSmith Agent Builder. Anyone can now build agents for complex daily tasks, without writing code. We built Agent Builder for anyone whose day gets swallowed by routine work. The research, follow-ups, updates, scheduling, and status checks that are essential to your operations, but quickly take over your calendar. Agent Builder is different from traditional workflow automations. You don’t need to map every step, tinker with if-this-then-that branching, or babysit dependencies. You just give it feedback like you would a teammate, and the agent learns using its memory. In this quickstart course, you'll learn how to: - Build an email agent - Understand what agents can do - Improve your agent - Set up triggers and your Agent Inbox Enroll for free ➡️

LangChain

26,513 views • 8 months ago

Everything Gets Rebuilt: my conversation with Harrison Chase, CEO of LangChain about agent harnesses, evals, runtimes, sandboxes, MCP and the future of the agent stack 00:00 Intro - meet Harrison Chase - at the Chase Center for the Daytona Compute conference 01:32 What changed in agents over the last year 03:57 Why coding agents are ahead 06:26 Do models commoditize the framework layer? 08:27 Harnesses, in plain English 10:11 Why system prompts matter so much 13:11 The upside — and downside — of subagents 15:31 Why a useful agent needs a filesystem 18:13 Additional core primitives of modern agents 19:12 Skills: the new primitive 20:19 What context compaction actually means 23:02 How memory works in agents 25:16 One mega-agent or many specialized agents? 27:46 The future of MCP 29:38 Why agents need sandboxes 32:35 How sandboxes help with security 33:32 How Harrison Chase started LangChain 37:24 LangChain vs LangGraph vs Deep Agents 40:17 Why observability matters more for agents 41:48 Evals, no-code, and continuous improvement 44:41 What LangChain is building next 45:29 Where the real moat in AI lives
46:57

Everything Gets Rebuilt: my conversation with Harrison Chase, CEO of LangChain about agent harnesses, evals, runtimes, sandboxes, MCP and the future of the agent stack 00:00 Intro - meet Harrison Chase - at the Chase Center for the Daytona Compute conference 01:32 What changed in agents over the last year 03:57 Why coding agents are ahead 06:26 Do models commoditize the framework layer? 08:27 Harnesses, in plain English 10:11 Why system prompts matter so much 13:11 The upside — and downside — of subagents 15:31 Why a useful agent needs a filesystem 18:13 Additional core primitives of modern agents 19:12 Skills: the new primitive 20:19 What context compaction actually means 23:02 How memory works in agents 25:16 One mega-agent or many specialized agents? 27:46 The future of MCP 29:38 Why agents need sandboxes 32:35 How sandboxes help with security 33:32 How Harrison Chase started LangChain 37:24 LangChain vs LangGraph vs Deep Agents 40:17 Why observability matters more for agents 41:48 Evals, no-code, and continuous improvement 44:41 What LangChain is building next 45:29 Where the real moat in AI lives

Matt Turck

35,253 views • 6 months ago

This 1-hour workshop on why your Claude Code runs out of tokens so fast will teach you more about making your sessions last longer than everything you've scrolled past this year. Bookmark this & watch, no matter what. After watching this, I built a CLI tool in Zig using that fixes the problem using Minimax-M2.7 on Claude code Here's how I built it; install it, then read the guide below by hoeem 🧵
1:02:22

This 1-hour workshop on why your Claude Code runs out of tokens so fast will teach you more about making your sessions last longer than everything you've scrolled past this year. Bookmark this & watch, no matter what. After watching this, I built a CLI tool in Zig using that fixes the problem using Minimax-M2.7 on Claude code Here's how I built it; install it, then read the guide below by hoeem 🧵

Avid

18,938 views • 5 months ago

Everyone’s building more AI agents. Almost nobody is building a way for them to share your memory. MemU just did. Your AI now remembers you across every device and every agent, getting smarter after every conversation instead of starting from zero. This changes how personal AI actually works. 👇
0:34

Everyone’s building more AI agents. Almost nobody is building a way for them to share your memory. MemU just did. Your AI now remembers you across every device and every agent, getting smarter after every conversation instead of starting from zero. This changes how personal AI actually works. 👇

Atul Kumar

80,364 views • 1 month ago

New short course: Long-Term Agentic Memory with LangGraph. Learn to build an agent with long-term memory in this course developed in collaboration with taught by its Co-Founder and CEO, Harrison Chase! Personal assistance and productivity tasks have become important use cases for agents. An important feature of an AI assistant, such as a coding or calendar assistant, is its ability to keep improving over time from its experience. Agent memory is the key capability that enables this. To add memory to an agent, you must first figure out what to store and what to retrieve when it is time to use the information. Additionally, you’ll have to decide when to update the stored information. For example, you might update in each iteration loop of the agent or perform updates in the background, with a helper agent. In this course, you will learn a mental framework to build agents with long-term memory. You'll create a useful email assistant that can respond, ignore, and notify using writing, scheduling, and memory-management tools. You’ll develop your agent's memory by adding facts to its memory store, provide examples to learn the user's preferences, and optimize system prompts to evolve instructions based on previous responses. In detail, you’ll: - Learn how the three types of memory--semantic, episodic, and procedural–and the two update mechanisms–via hot path and in the background–apply to your agents. - Build an email agent with writing, scheduling, and availability tools, along with a router that triages incoming email and handles it accordingly by ignoring, responding, or notifying the user. - Add tools to your email agent that allow it to operate on semantic memory by learning facts about the user, storing them in a long-term memory store, and searching over them in future interactions. - Incorporate episodic memory, in the form of few-shot examples, in the triage step of your agents to help them learn and update user preferences. - Add procedural memory as system prompts, optimized with feedback to improve the instructions the agent follows. Learn how to approach memory in agents, and start building agents with long-term memory with LangGraph! Please sign up here:
2:06

New short course: Long-Term Agentic Memory with LangGraph. Learn to build an agent with long-term memory in this course developed in collaboration with taught by its Co-Founder and CEO, Harrison Chase! Personal assistance and productivity tasks have become important use cases for agents. An important feature of an AI assistant, such as a coding or calendar assistant, is its ability to keep improving over time from its experience. Agent memory is the key capability that enables this. To add memory to an agent, you must first figure out what to store and what to retrieve when it is time to use the information. Additionally, you’ll have to decide when to update the stored information. For example, you might update in each iteration loop of the agent or perform updates in the background, with a helper agent. In this course, you will learn a mental framework to build agents with long-term memory. You'll create a useful email assistant that can respond, ignore, and notify using writing, scheduling, and memory-management tools. You’ll develop your agent's memory by adding facts to its memory store, provide examples to learn the user's preferences, and optimize system prompts to evolve instructions based on previous responses. In detail, you’ll: - Learn how the three types of memory--semantic, episodic, and procedural–and the two update mechanisms–via hot path and in the background–apply to your agents. - Build an email agent with writing, scheduling, and availability tools, along with a router that triages incoming email and handles it accordingly by ignoring, responding, or notifying the user. - Add tools to your email agent that allow it to operate on semantic memory by learning facts about the user, storing them in a long-term memory store, and searching over them in future interactions. - Incorporate episodic memory, in the form of few-shot examples, in the triage step of your agents to help them learn and update user preferences. - Add procedural memory as system prompts, optimized with feedback to improve the instructions the agent follows. Learn how to approach memory in agents, and start building agents with long-term memory with LangGraph! Please sign up here:

Andrew Ng

132,058 views • 1 year ago

Anthropic engineer just dropped a full walkthrough on building AI agents from scratch this single video is worth more than any $600 AI agents course here's what she covers: > what Agent, Environment, and Session actually mean > how to stream live events from your agent > wiring up custom tools from scratch > the server-side loop that makes agents actually work > roadmap to subagents, vaults, and memory 37 minutes that will answer every question you have about building agents the people who understand what Claude can actually do are building things everyone else thinks requires a whole team most of them aren't smarter, they just know features that most people have never heard of full breakdown on every Claude feature worth knowing in the article below
36:49

Anthropic engineer just dropped a full walkthrough on building AI agents from scratch this single video is worth more than any $600 AI agents course here's what she covers: > what Agent, Environment, and Session actually mean > how to stream live events from your agent > wiring up custom tools from scratch > the server-side loop that makes agents actually work > roadmap to subagents, vaults, and memory 37 minutes that will answer every question you have about building agents the people who understand what Claude can actually do are building things everyone else thinks requires a whole team most of them aren't smarter, they just know features that most people have never heard of full breakdown on every Claude feature worth knowing in the article below

Anatoli Kopadze

39,240 views • 3 months ago