Loading video...

Video Failed to Load

Go Home

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 views • 3 months ago •via X (Twitter)

31 Comments

Gipp 🦅's profile picture
Gipp 🦅3 months ago

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

Codez's profile picture
Codez3 months ago

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

Spivach's profile picture
Spivach3 months ago

free Anthropic courses and this == cheats

Codez's profile picture
Codez3 months ago

yeah, soo true !

Fokki's profile picture
Fokki3 months ago

Real talk

Codez's profile picture
Codez3 months ago

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

Yarchi's profile picture
Yarchi3 months ago

this is a brilliant vid man

Codez's profile picture
Codez3 months ago

yeah bro, super useful for me too

Sunwoo Park's profile picture
Sunwoo Park3 months ago

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.

Jordan Taylor's profile picture
Jordan Taylor3 months ago

@ShenSeanChen

Damir Akaza's profile picture
Damir Akaza3 months ago

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

shmidt's profile picture
shmidt3 months ago

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

Codez's profile picture
Codez3 months ago

yeah bro, you nailed the right setup !

Hussain Hashim | Building SundayBack's profile picture
Hussain Hashim | Building SundayBack3 months ago

@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.

Makaroni's profile picture
Makaroni3 months ago

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

ZFLOW AI's profile picture
ZFLOW AI3 months ago

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.

AI Mastery Guide's profile picture
AI Mastery Guide3 months ago

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.

Nostaline's profile picture
Nostaline3 months ago

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.

expemilly's profile picture
expemilly3 months ago

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

rewind's profile picture
rewind3 months ago

episodic memory is underrated

z3n's profile picture
z3n3 months ago

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.

Luís Rodrigues's profile picture
Luís Rodrigues3 months ago

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

maguyva's profile picture
maguyva3 months ago

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

AI Apps API's profile picture
AI Apps API3 months ago

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.

Roan's profile picture
Roan3 months ago

brilliant share as always codez

Electrik Dreams's profile picture
Electrik Dreams3 months ago

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.

Harry Tandy's profile picture
Harry Tandy3 months ago

that architecture is exactly how we build smart agents

Gregor's profile picture
Gregor3 months ago

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?

liquidated (Dev Arc)'s profile picture
liquidated (Dev Arc)3 months ago

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

Nabeel K.'s profile picture
Nabeel K.3 months ago

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.

Dipanshu Kushwaha's profile picture
Dipanshu Kushwaha3 months ago

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

Related Videos