From 81c82d9b9367f930b01812f578c01219f370906e Mon Sep 17 00:00:00 2001
From: Chris Latimer <chris.latimer@vectorize.io>
Date: Wed, 28 Jan 2026 19:21:15 -0700
Subject: [PATCH] README tweak

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 053cc09f..d74c3771 100644
--- a/README.md
+++ b/README.md
@@ -137,7 +137,7 @@ The requirements for this use case usually look something like this:
 
 ![Per-User Memories](./hindsight-docs/static/img/per-user-memory-requirements.png)
 
-<video src="https://github.com/user-attachments/assets/4805e8e1-e7d1-47c6-a4f8-2344a5ec8906" controls></video>
+<video src="https://github.com/user-attachments/assets/923b798d-3581-4897-bb62-9cfa5a931682" controls></video>
 
 Satisfying these requirements in Hindsight is straightforward. When new user inputs and tool calls are ingested into Hindsight using the retain operation, custom metadata can be used to enrich the new memories. Metadata provides a convenient way to isolate memories that need to be restricted to a given user. Once these are fed into the retain operation, any raw memories and mental models that get created can be filtered when retrieving relevant memories.