WEBVTT 00:00:00.160 --> 00:00:07.760 Claude code is great, but we also know it's only great in the session. Anytime we pick back up, we've lost everything out of the last session. 00:00:07.920 --> 00:00:09.440 This is ClaudeMem. 00:00:09.440 --> 00:00:16.815 It gives Claude code persistent and compressed memory across sessions while auto capturing stuff like bug fixes and decisions, 00:00:16.975 --> 00:00:24.975 then brings that context back right when we need it. All open source, no API keys. We have videos coming out all the time. Be sure to subscribe. 00:00:30.310 --> 00:00:41.590 The setup here is really quick, and you can get all this from the Claude MEM repo. I'll assume you already have Claude code installed as I do, so adding Claude MEM is basically two commands inside Claude. 00:00:41.875 --> 00:01:29.160 First, fire up Claude, then just run this command right here. After that, we can install it with the command right here. Both of these I got off the repo. I'm gonna restart Claude and you're done. That is Claude mem right on your system. I didn't have to play around with any config files or API keys, which is a huge bonus. And here's the part I really like. It runs locally, so all this data it's capturing is staying on your machine. Alright. Let me actually show you all the good stuff here. It'll be quick so you can get the gist of it because that's what matters. We're inside a fresh project folder, just some fast API I was messing around with, but for this, we're gonna make a super basic Python script just to cover the point. In the first session, I'm gonna ask Claude to create a recursive fibonacci py file, but skip handling negative inputs. 00:01:29.960 --> 00:01:38.725 As expected, Claude generates the file and opening it, it all looks good. So now I'm gonna run with this and I'm gonna say I'll run it with a negative number. 00:01:39.365 --> 00:01:45.525 For obvious reasons, we get an error. So I'll just tell Claude add a value error when n is negative. 00:01:46.660 --> 00:02:05.915 Claude updates the code, I rerun it, clean error message, the bug's fixed. Okay. Now here's the thing, Claude can do that, that was super easy. While we're doing that though, Claude mem is quietly watching in the background. It's logging what just happened. This runs completely locally on your local host so it's always refreshing. 00:02:06.075 --> 00:02:21.020 We can do things here like the bug, right, I can view this, I can view the fix, the reasoning, and the code diff. This is really the whole ClaudeMem web UI and you can see real time entries that are categorized and there's our bug fixed. 00:02:21.180 --> 00:02:28.620 So now comes the real test because the first part is already nice. It was cool, right, to see this, but basically it's just nice looking logs. 00:02:29.045 --> 00:02:35.525 I'm gonna go in here and I'm gonna end the current session, I'm gonna clear out my terminal, and I'm gonna fire back up Claude. 00:02:36.085 --> 00:02:45.730 Now that I'm in a new session, so I'm gonna ask Claude to pick back up where we left off. Let me just ask it to recall the Fibonacci bug we fixed last time. 00:02:47.170 --> 00:02:59.135 And there it is. It's pulling in that context. Claude pulls the exact fix back without me explaining the whole story again. And I can go one step further, I can ask it to search for Fibonacci bug fix. 00:03:00.175 --> 00:03:05.055 Now I get the compressed summary and if I expand it, I get the full context. 00:03:05.295 --> 00:03:12.070 I don't have to waste time here copying and pasting or trying to re explain what we were doing before, it just remembers. 00:03:12.230 --> 00:03:26.255 This is huge because now we can enter new sessions, leave these sessions, and Claude Memm is running in the background to help us out. There are a lot of things here that I love that are gonna help you out. First, it saves a huge amount of time, so you can stop reloading context every session. 00:03:26.655 --> 00:03:29.375 Then it's actually pretty token efficient. 00:03:29.615 --> 00:03:42.440 CloudMem compresses memories by up to 10 x so we aren't hitting our limits as fast as we once were. Finally, you can actually find stuff. You can search memories by integrated tags that we have in ClaudeMemp. 00:03:42.440 --> 00:03:46.520 Type things like bug fix or decision, file path or keywords, 00:03:46.600 --> 00:03:48.280 that pops up in our UI. 00:03:48.360 --> 00:03:55.445 That's what makes this really useful to us in these larger projects and unlike Clog's basic memory file, this is automatic. 00:03:55.525 --> 00:04:14.015 Plus it's open source, so if you wanna tweak it, you can. Long story short, that's Clog MEM. Right? Clog memory, Clog MEM saves us time. This is ideally a tool to speed up your workflow and save you a bunch of tokens. Try it out on your project, I think you'll immediately feel the difference. If this helped, be sure to hit that subscribe button and we'll see you in another video.