Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Ex-Google engineer explains how to build memory for self-improving AI agents in 12 minutes. procedural (how to act / skills) + semantic (durable facts / profile) + episodic (dated events / chat history). Memory is an important part of an agentic loop. Memory + loops + harness + evals...

90,000 Aufrufe • vor 3 Monaten •via X (Twitter)

31 Kommentare

Profilbild von Gipp 🦅
Gipp 🦅vor 3 Monaten

creating a memory for self-improving AI agents is the best solution he has ever created

Profilbild von Codez
Codezvor 3 Monaten

Yeah, that’s definitely a really important part of agentic loops.

Profilbild von Spivach
Spivachvor 3 Monaten

free Anthropic courses and this == cheats

Profilbild von Codez
Codezvor 3 Monaten

yeah, soo true !

Profilbild von Fokki
Fokkivor 3 Monaten

Real talk

Profilbild von Codez
Codezvor 3 Monaten

Yeah, real alpha from a senior engineer, real use cases, not just buzzwords.

Profilbild von Yarchi
Yarchivor 3 Monaten

this is a brilliant vid man

Profilbild von Codez
Codezvor 3 Monaten

yeah bro, super useful for me too

Profilbild von Sunwoo Park
Sunwoo Parkvor 3 Monaten

The memory point is underrated. The useful version is not just “give Claude more notes,” it is deciding what becomes durable memory, what gets retrieved, and what should expire before it pollutes the next run.

Profilbild von Jordan Taylor
Jordan Taylorvor 3 Monaten

@ShenSeanChen

Profilbild von Damir Akaza
Damir Akazavor 3 Monaten

Already bookmarked it, I absolutely love this kind of useful content, maybe I'll learn something myself

Profilbild von shmidt
shmidtvor 3 Monaten

procedural + semantic + episodic is such a clean mental model for this

Profilbild von Codez
Codezvor 3 Monaten

yeah bro, you nailed the right setup !

Profilbild von Hussain Hashim | Building SundayBack
Hussain Hashim | Building SundayBackvor 3 Monaten

@0xCodez interesting breakdown! never thought about how memory types play a role in AI loops. makes me wonder how close we are to AI that can really adapt on its own.

Profilbild von Makaroni
Makaronivor 3 Monaten

the 3 memory types breakdown is genuinely solid agents without episodic memory are just goldfish with a system prompt

Profilbild von ZFLOW AI
ZFLOW AIvor 3 Monaten

One challenge that doesn't get talked about enough is memory efficiency. As agents take on longer tasks, storing and retrieving the right information efficiently becomes increasingly important.

Profilbild von AI Mastery Guide
AI Mastery Guidevor 3 Monaten

Splitting memory into procedural, semantic, and episodic is the part most agent tutorials skip, that structure is what actually makes recall useful instead of just a growing log file.

Profilbild von Nostaline
Nostalinevor 3 Monaten

Encountered AtomicMemory and its philosophy resonates. Open source, self-hosted infrastructure for auditable memory. Rather than trusting closed systems, you maintain direct control and visibility.

Profilbild von expemilly
expemillyvor 3 Monaten

actually, even though it's tedious, it's a very useful thing

Profilbild von rewind
rewindvor 3 Monaten

episodic memory is underrated

Profilbild von z3n
z3nvor 3 Monaten

The procedural/semantic/episodic split is the right taxonomy, and it's where most agent stacks are thinnest. Everyone bolts on a vector store for episodic recall and calls it memory. Procedural memory (learned skills, not just retrieved facts) is the part that actually compounds.

Profilbild von Luís Rodrigues
Luís Rodriguesvor 3 Monaten

The biggest takeaway is that memory isn't just storing chat history. Different types of memory solve different problems.

Profilbild von maguyva
maguyvavor 3 Monaten

episodic memory is the one people skip until context windows blow up. it's what scales session count.

Profilbild von AI Apps API
AI Apps APIvor 3 Monaten

The split matters because each type earns its keep differently. Episodic is the one most builds skip, and it is exactly what makes run 50 cheaper than run 1. One thing we learned shipping this: keep embeddings local. Recall gets so fast the model stops treating memory like an expensive last resort and starts calling it constantly, which is when agents actually start compounding.

Profilbild von Roan
Roanvor 3 Monaten

brilliant share as always codez

Profilbild von Electrik Dreams
Electrik Dreamsvor 3 Monaten

Most teams get stuck on retrieval. The hard part is consolidation: what to retain, compress, or discard after each session. The summarizer loop is the actual product.

Profilbild von Harry Tandy
Harry Tandyvor 3 Monaten

that architecture is exactly how we build smart agents

Profilbild von Gregor
Gregorvor 3 Monaten

hit this exact wall with my finance app deprecated a skill in procedural memory but episodic wasn't triggering a rewrite so the old behavior kept firing for like 3 days before i caught it. did he cover invalidation logic, or just how to build the three layers?

Profilbild von liquidated (Dev Arc)
liquidated (Dev Arc)vor 3 Monaten

built forge and i had to figure this out myself fr, memory is the hardest part

Profilbild von Nabeel K.
Nabeel K.vor 3 Monaten

The taxonomy is the easy part. The hard part nobody demos in 12 minutes is consolidation: deciding what episodic noise gets promoted to durable semantic memory and what gets forgotten. Without that filter, memory just becomes a slower context window.

Profilbild von Dipanshu Kushwaha
Dipanshu Kushwahavor 3 Monaten

Nice framework. Memory + loops = powerful combo for smarter agents. Excited to see how this speeds up real-world progress.

Ähnliche Videos