i gave AI a memory upgrade—and found a serious problem | HINDSIGHT review — Transcript
Full transcript
- 0:00Okay, so let's talk about Agent Memory today,
- 0:03because I've been going deeply on this lately.
- 0:05I went through two open source memory systems back
- 0:07to back, and after leaving with them for a while,
- 0:10the feeling is complicated. There is this part
- 0:13where I'm like, wow, he actually remembered that.
- 0:15And then there's this other part where I'm
- 0:17like, I never said that. So this video isn't a
- 0:21recommendation. I'm not going to see here
- 0:23telling you to install hindsight or any other memory
- 0:25system right now. I just want to walk you
- 0:27through what it's actually like to use one.
- 0:30Actually, hold on, let me back up a bit. Before
- 0:32I get into hindsight, I want to talk about why I
- 0:34wanted the memory system in the first place.
- 0:37Because you might be thinking, it's just memory,
- 0:39right? We used to make a few markdown
- 0:41files, write things down, where is the big deal?
- 0:43That's exactly what I thought at first. Then I
- 0:46found out I had underestimated it. Anyone who
- 0:48used an agent for a while already knows. The
- 0:51difference between an agent that remembers and
- 0:53doesn't is huge. And the weight of that difference is not the same for every agent.
- 0:58Some of them you only use to write code, say
- 1:01DeepSeek or Codex. For those remembering
- 1:04what happened inside this project is enough.
- 1:07You only need project level memory, but a personal
- 1:09assistant agents like Hermes, that's not just
- 1:11a tool for writing code. It handles my life,
- 1:14my work, my creative work. So what it needs to
- 1:16remember isn't one project, it's me. And that
- 1:19pushes my requirement on its memory up a
- 1:21whole notch. Let's be clear, Hermes is not without
- 1:24memory. It has memory, it's actually known
- 1:27for its memory. That memory lives in a document
- 1:30called memory dot MD. And that document has
- 1:32a ceiling on it 2200 characters by default,
- 1:36it's so limited, you write two paragraphs and
- 1:38you're out. So it keeps writing and then deleting
- 1:40the old stuff, squeezing in new stuff,
- 1:42condensing over and over. Put bluntly, it can hold a short
- 1:47about you, what you like how you tend to work
- 1:50and the occasional project detail. Anything beyond
- 1:52that, you're done. The capacity is just what it
- 1:55is. These days, I watched you tell me the memory
- 1:57is full several times a day, and then
- 1:59something gets delayed to something gets condensed, it
- 2:02either shows everything in or gives up and here
- 2:05is the interesting thing. I finally opened memory
- 2:08dot MD myself one day, everything in there
- 2:10had been condensed into something like an
- 2:12ancient literature. I couldn't even read it. And
- 2:15Hermes defaults that memory dot MD that small for
- 2:18a reason, you can raise it sure. But the
- 2:20default is small because every time you open a new
- 2:23conversation, that whole memory file gets sent
- 2:26again, it just hands in your context the entire
- 2:28time. So anything you put in there that isn't
- 2:31about the current project, there's two things,
- 2:33it pollutes your context, and it burns tokens for
- 2:36absolutely nothing. So is 2200 characters enough?
- 2:40Well, for most people who's just playing with
- 2:42this, I think it is. Hermes can afford to keep
- 2:44its memory that light because it has other
- 2:47tricks. There is a skills or one skills aren't really
- 2:50memory strictly speaking, but they hold a ton of
- 2:53detail about how to do specific kinds of tasks.
- 2:55Having one of those for a regular job is honestly
- 2:58enough most days. And if it really isn't enough,
- 3:00there is one last layer when it needs to
- 3:02find something, it can go dig through the entire
- 3:05session history, everything you told it and
- 3:07everything it said back, all of that sitting in
- 3:09a database, when it has to, it goes in there.
- 3:12And honestly, it's pretty accurate. So Hermes setup
- 3:14isn't bad day to day, it's genuinely enough.
- 3:17Once you get to where I am, dozens of conversations
- 3:20every day, and you let that pile up for months,
- 3:22you start to feel the friction. It's really hard
- 3:25for you to find something you said before or
- 3:26your deep before the data is just too big, you're
- 3:29needling his tech in it and that waste time with
- 3:32tokens and drag samples accuracy and speed. So for
- 3:35me using a personal agent heavily over a long
- 3:37stretch, long term memory is still one of the
- 3:40clearest gaps to close that gap. I went and
- 3:43looked at the open source project called hindsight.
- 3:46Hindsight means looking back after the fact.
- 3:48I like the name, which honestly fits what the
- 3:50product is doing. So what is hindsight exactly?
- 3:54You can think of it as a long term memory layer
- 3:56built for agents. The core is three verbs
- 3:59retain, recall, reflect, remember, look it back up,
- 4:03and there isn't over the memories to form a
- 4:05judgment. And underneath, it isn't just storing
- 4:08text when a conversation comes in, it pulls out
- 4:10whatever seems worth remembering around embeddings,
- 4:14build relationships between people and events
- 4:16and records the timing too. So when you ask the
- 4:18question later, it isn't searching keywords, it
- 4:21goes out from semantics, relationships and the
- 4:24time at the same time, then stitches the most
- 4:27relevant memories back together, which makes it
- 4:29feel like an external memory organ hanging off
- 4:31the back of the agent. The agent handles talking
- 4:34and working hindsight sits back there quietly
- 4:36remembering pulling every conversation apart,
- 4:39summarizing it, weaving it into a web of memory. And when you need to look back,
- 4:44it pitches the relevant parts out. Let me show
- 4:46you what that looks like. I was testing a model
- 4:48called the space bunny at the time and I casually
- 4:51asked one question, what do I actually think about
- 4:53this model? It went through hindsight, recalled
- 4:56and put together a pretty complete memory right
- 4:59on the spot and the accuracy held up, not word
- 5:01for word, but close enough. All of it was genuinely
- 5:04things I'd said or things I'd talked through
- 5:06with the agent, my reaction at the time, what I'd
- 5:09actually done, how I changed my mind. So my
- 5:12reaction at the time was like, this thing is real,
- 5:15it works. I still kept an eye on it though. I
- 5:17asked the follow up question, did you pull all
- 5:19that from the memory or did you go dig through
- 5:22some other files? Because that's Hermes's habit,
- 5:25you give her a task he doesn't know about and go
- 5:27searching session history for keywords and then
- 5:30pieces something together out of them. And he said
- 5:32no, the result was from hindsight only. Think about
- 5:35that, no session search at all. And it still handed
- 5:37me my entire take on one thing in a single answer.
- 5:40That's what a memory system actually buys you. As
- 5:43a comparison, I asked it to do the same job with
- 5:46hindsight turned off. It was noticeably
- 5:48slower. You can see it went through dozens of files,
- 5:50it took forever to produce a similar answer
- 5:53and the fact that it could produce one at all
- 5:55is largely because I happen to have a written
- 5:57transcript about space bunny already. Plus the
- 5:59daily conversation logs my agent and I generated
- 6:02it just found those files and summarise it for me
- 6:05again. So same destination, completely different
- 6:09experience getting there. Now, a normal project
- 6:11intro video would probably end right about here.
- 6:14Memory system, it's great, go use it. See you next
- 6:17time. But anyone who's watched my video for a
- 6:19while knows the real experience of running something
- 6:22better doesn't go that smoothly. Things break.
- 6:24And the thing that broke is exactly why I can't
- 6:27recommend this system to you outright. And why I
- 6:29personally hide on fully trusted high bar. Because
- 6:32it will remember the wrong things very seriously.
- 6:35During one writing session, I had the agent to go
- 6:37look up some material. My agent pulled a video,
- 6:40summarised it from the subtitles, I handed me the
- 6:42information. Some other creator runs a batch of
- 6:45experiments plus their opinions on it. There was
- 6:48never me seeing anything of my agent find all of
- 6:51that on its own. But when I asked for memories to
- 6:54work from, it had recorded it as me running the
- 6:56experiments and me making the judgment. It learned
- 6:59to invent a life history for me. Honestly, that
- 7:02part is a little unsettling because this happened
- 7:05yesterday. So I can point out exactly where it
- 7:07went wrong. Or if it had happened six months ago,
- 7:10or even a year ago, and I don't remember it
- 7:12anywhere near that clearly myself. If that can't
- 7:15be fixed, the system isn't trustworthy. So I went
- 7:18back and traced it. And it turns out that at the
- 7:20level of how it works, this kind of error is
- 7:23hard to avoid. Because this memory system takes each
- 7:26conversation between me and the agent summarises
- 7:29it attributes it then links it up. And the moment
- 7:31the context gets long and the roles aren't
- 7:34separated clearly enough, say all the you he and it that
- 7:38showed up in a conversation of a few times me and
- 7:41the agent in that session obviously know who those
- 7:44pronouns point to. But the memory system only
- 7:46sees that one turn so you can very easily map that
- 7:50eat onto the wrong person. My workaround for
- 7:53now was to modify Hermes's Hindsight plugin.
- 7:56So when it hands a conversation over to
- 7:58hindsight summarize, it clearly marks which lines were me
- 8:02and which came from the agent and reserves
- 8:04every pronoun whether that helps out no, it's an L I
- 8:08m everything's everything is a probability.
- 8:11But at least next time we make something up,
- 8:13I'll trace it faster than this time. And there
- 8:15were two smaller problems. I Wow, not as bad as
- 8:18inventing a life history. But annoying enough
- 8:20that I want to mention them. The first one is
- 8:23maintenance. The whole system isn't something
- 8:25like a simple skill. It's infrastructure you have to
- 8:28raise yourself and the chain is long on top of
- 8:30being external. It's not like a memory dot MD,
- 8:33where your Hermes Agent writes one sentence and
- 8:35that's it. It has to pull your turn apart first,
- 8:38then summarize it with an L M, then my
- 8:41embedding, build the index and store all of it in its own
- 8:44memory system. And then when something needs to
- 8:46recall it, that's another set of moves. And that's
- 8:49the simplified version. In practice, there's more
- 8:51moving parts than that. The chain that don't means
- 8:54any link in the middle can break and then either
- 8:57you never got stored or it never gets called the
- 8:59worst one I hid was that it breaks silently. You
- 9:03have no idea at all. My hindsight had just been
- 9:05deployed. I spent the first day thinking it was
- 9:07working. Then the next day I call it an entire
- 9:10previous day of memory was just empty. It turns
- 9:13out that there's a silent bug in the plugin. So
- 9:15during all of my conversations, the previous
- 9:18day, nothing got sweetened, but it reported nothing.
- 9:20But bugs like that usually don't come back once
- 9:23you've fixed them. So I think that's an acceptable
- 9:25trade. And the other one is latency. It's an
- 9:28external system. So you don't get the memory the
- 9:31second you finish talking, it might be ready the
- 9:33next turn or the one after that. And that's also
- 9:36something you just just have to live with. So you
- 9:39might be put off by now, or you might be dying to
- 9:41try it if you're a tinkerer like me. But
- 9:44before you go tinker, here's what running this thing
- 9:46actually costs me. It's open source. And thank God
- 9:49for the open source community and everyone in it.
- 9:51But open source doesn't mean it's free to
- 9:53run. Settling aside the machine and the disk,
- 9:56it's four bills. Bill one is summarization. Every
- 9:59single turn goes through an LLM, you can configure
- 10:02it to every few turns or even every few steps,
- 10:05depending on how much detail you want to keep. And
- 10:07bill two is embedding. If you've got the hardware,
- 10:10you can run it local. If you'd rather not bother,
- 10:13you can use the cloud. And honestly, the cloud is
- 10:15very cheap, like pennies a day. And bill three is
- 10:18re ranking once you have 10s of 1000s of
- 10:20memories. Once every relevant stuff is retrieved, you need
- 10:24a general ranker to resource everything by
- 10:26relevance. So the result is actually usable. And bill four is
- 10:30deployment resources. In practice, one core CPU and
- 10:33two gigabytes of RAM will not run this comfortably,
- 10:36because your cloud server isn't running
- 10:38hindsight alone. You have Hermes in there, plus whatever
- 10:41else you deploy yourself. I bumped it to two
- 10:44core CPU and four gigabytes of RAM. And that barely
- 10:47works. And that's with the Linux version they have,
- 10:49because my particular VPS is already tight on disk.
- 10:52I just I just have too many things on it. So the
- 10:54full database and all the dependencies were a bit
- 10:57too much. So put it all together. There are costs
- 11:00and there are things that's not so great about it.
- 11:03But I do plan to keep using it for exactly one
- 11:05reason. It actually feels the gap in Hermes's memory,
- 11:09a memory web that writes itself in continuously
- 11:11with timestamps with original text, summarized and
- 11:14linked a single MD file just cannot do that. What
- 11:18this kind of memory system actually gives you isn't
- 11:20making the agent smarter on the spot. It's
- 11:22quietly sorting through everything you've said, done and
- 11:25thought about ahead of time. And then later when
- 11:27around the task and you need something, you notice
- 11:30it remembers more accurately. It gets what you
- 11:32want better. And it understands why you made a
- 11:35decision back then. Because everything you see
- 11:37right there in the memory web, instead of you
- 11:39searching a session from three months ago. So this
- 11:41thing has to be raised. Your memory accumulates a
- 11:44day at a time, kind of like keeping a plant.
- 11:47If you stare at it every day and you feel like
- 11:50there's nothing happening, nothing is changing.
- 11:52But when you come back a month later, you'll find
- 11:55it's dead. Just growing; it's more alive. So
- 11:57that's it for today. If you got something out of this,
- 11:59leave a like and don't forget to subscribe.
- 12:01If not, watch another one. See you next time.
About this transcript
This page contains the full transcript of i gave AI a memory upgrade—and found a serious problem | HINDSIGHT review by y8y.systems, generated from the public captions YouTube serves with the video. The transcript has 2,428 words across 274 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.
What you can do with it
Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to choose a caption track available on the video.
Free YouTube transcript tool
YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, caption language selection, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.