I Fixed My GrokBots Memory, You Should Do The Same.

0:00Rockbot is one of the best personal agents on the market, but its memory is awful. Change a rule and it can end up holding the old rule and the new one at the same time. And there's no memory screen in the app where you can see what it remembers and fix it. If this is your first time here, my name is Casper. I'm the founder of Deeprooted AI. I use these tools every single day to run my entire business, and I build them out for paying clients. My goal for this video is simple. I'm going to fix my own Grockbot's memory and show you every single step. By the end, you'll know

0:25exactly how to see what your bot remembers, how to clean up the stuff that's wrong, and you'll get a bot that does all of that for you. So, get comfortable, grab some coffee, and let's hop straight into the video. Okay, we're diving straight in. And the first thing that I'm going to do is go to my chief of staff bot, and I want you guys to type in a similar prompt that I'm typing into right now. Yours could be a little bit more in-depth. I obviously have to protect some information because this bot knows everything about me. But what I'm going to have it do is say, "List

0:49what you remember about my bots, crew, and house rules. Grouped by topic. for each show the current version and any older or conflicting versions do not change anything. I'm going to send this off and we're going to get a result and we're going to see exactly where old rules and new rules are stored because I know I have some in here. Our chief of staff returned a pretty lengthy response. So, we're going to be pretty quick going through this. Right now, we

1:09can see the crew size is incorrect one. This one says 20 bots. The other one right here still says 18. We still have some different names in here as well. And right here, you can see that makes 21 that I can message. So, the correct number here is 21. But in my bots's memory, there's 18 and there's 20. Then we have a list of all our current bots and exactly what they do. So we're missing a few right here. You can see these were added on October 3rd. And we also have one more that we added

1:32yesterday. So that one's missing here. Then we have the removed or frozen section where we have certain bots that we've taken off the team and we've removed. And then here we have some of our basic house rules that we have stored inside of an agents.md file inside of the Grockbots computer. So these all look accurate. And then here are the older versions and the gaps. So, we can see that in our Grockbots's memory, there's a ton of contradicting information. Now, I always like to kind of test the bot and see which information it's actually choosing. So, I'm going to prompt it really quick and say, "When my house rule file and your

1:59memory disagree, which one do you follow?" So, I'm going to go ahead and send that off and we're going to see how my chief of staff bot actually makes decisions when there's contradicting rules. And here's the chief of staff's response. It says on the lines the house rule file actually covers the file wins. That means sends, money lanes, publishing values, and which computer is home. Most of what looks like disagreement is really a gap. The things you cut from the file like Mike Nochase, affirm, the school handoff, and the Jeb freeze aren't contradicted by it. The file just doesn't mention them. So, obviously, I've taken care of this

2:28pretty well, but there are some gaps that I need to figure out. Now, of course, I have 21 different bots. A lot of you might just have two or three bots doing specific tasks. And for you guys, this would look like changing your business hours and your Grockbot mentioning the old one. Still hopping back into Grockbot. If we go ahead and click on our chief of staff bot and open up its kind of settings, we can see its computer. We can see the library and all the files that it stores. And then we have details here. And inside of details, you can see that there's no

2:53memory file. There's no soul.md like you would see in something like Hermes. Even the new Muse agent has a very simple section where it has a memory and soul.md file. That just doesn't exist in Grockbot. In Grockbot, how memory works, all the bots actually store specific notes and write them by themselves. So, when you change a specific rule and you don't prompt it to remove the old one, it keeps both of them. And as of right now, there's no way to change that besides prompting your agent and being diligent when you're changing certain settings and memories. I've mentioned it already, but another very popular harness like Hermes actually stores its

3:23memory in two separate files. So, right here, as you can see, I just told it to pull up our memory. MD file. I can actually open a preview and go ahead and manipulate that myself. I'm not going to cuz there's some sensitive information in there. But I can open up all these files and actually manipulate them and see exactly where my agent's getting its information from. Hermes also works really well because if you hop into memory and context, you can see that you can connect it to a memory provider like Honcho where all your memories and conversations get stored inside of a cloud and you can query them at any

3:50time. This is the only reason right now that I still think Hermes has a slight edge over Grockbot. Now, I'm not saying that Grockbot doesn't have memory files. It's just they're a lot harder to find and you can't actually manipulate them yourself. So, if I hop into the file manager on Grockbots's computer right now and I go over to devices here and then I click on agent data and I see agents right here, I can click into them and each of these agents has their own files like profile.json, settings.json, and I can go into here and click on these. Like you see, it's going to open

4:17all this up. And here's all the information that we can see. And we could actually manipulate this, but again, it's in the Grockpots computer. It's a lot harder right now. It is easier to just simply prompt it. Like I said, if there was just a tab or in the detail section of all these agents, their memory MD files and their soul.md files, I feel like that would be much easier. Now, this is also a shared memory versus a bot memory problem. And I'll show you the difference here in a second. A lot of people think your bot is actually forgetting this information, and that's not the case at all. What's

4:44really happening is it's holding two versions of the same information and picking the wrong one. So, let's go ahead and clean it up. What we're going to do here is paste in a similar prompt that we pasted in earlier. But this prompt is telling my chief of staffbot to read every single memory it has about me regarding my bots, regarding rules, anything like that. Grouping them by topic, showing me any older versions compared to the newer memories that we have. And then proposing changes to me without actually changing anything until I approve it. Now that I'm thinking of it, I probably could have grouped these prompts together and saved a little bit

5:10of my usage, but oh well. We're going to go ahead and send this one off and we'll see what it comes back with. Grockbot has been extremely fast lately. The Grockbot team is absolutely killing it with some of these updates and it's just going so fast right now. So, this is great. But, I've read through all of it. There are 11 topics and I'll take them one at a time. Here is topic one, you and the family. There's some older conflicting information right here. What I act on without asking. So, this is a proof topic one changes. So, it's going to go through all 11 topics. So, here

5:35are some of the older or conflicting ones. An earlier note calls my fiance's name Kylie and it's actually spelled incorrectly. And then I have the same identity note saved twice. One copy says I'm not yet named in vault files. That's stale. So, what it's proposing is that I call you captain and I use Kylie and botchi by name and replies and in-house rule files. Nothing else here triggers any action on its own. I don't send anniversary or birthday reminders unless you ask. So, I'm just going to go ahead and approve this topic. Now, at first, this might feel extremely tedious, but that's just part of managing your AI

6:02agents and managing their context and memory properly. But the fortunate thing is we only really have to do this once. And then when I'm done with this, I'm going to show you the actual rule that I'm going to put in so that I don't have to do this as often next time. So once I'm done going through all 11 topics, I'll get back to you guys and we'll get to that prompt. Now I'm making my way through these topics and I realized I was approving it without making any changes. So I went back and I said, "Hey, fix all the stale, contradicting or older information and remove them

6:25from the memory files. Make sure you guys do the same. It's very important to read instructions and not just act. Learn from me." Okay, so about 15 minutes later, I went through all 11 topics of my chief of staff bots memory and I went through everything. We fixed all the contradictory information. We removed any conflicting information. we got fully updated and now we're all on the same page. Now, I thought I was doing a pretty good job of handling this, but I was very wrong. There was a ton of stale and conflicting information and I was just doing myself a disservice. So, I'm very glad that I did

6:53this. And now that we've completed that for this bot, we can give it the prompt of saying when I say this replaces the old rule, delete the old version from your memory. If I say to add something, I want you to check your memory for something similar before adding it. We want to avoid conflicting information. I'll send that off. And now my bot will have this rule. I'm hoping it just adds it to the house rules. We're gonna see if that happens. But right now it says got it and it's saved. When you say this replaces the old rule, I'll delete the old version before I add anything. I'll

7:20check memory for anything similar and fix or remove it first so nothing conflicts. So now it's saved that in its memory and not actually the house rules. The only thing here when it says it's saved, I want to know where it's exactly saved. So I'm going to go ahead and ask that. And after asking it, you can see it's in my own agentwide memory saved as a profile note. I keep those on my mind on every turn in every chat with me. If you want the whole crew to follow it, I can add it to your house rules file, which is exactly why I wanted and that's

7:45why I asked this question. So, we're going to go ahead and add it to the house rules file. And it's going to be in both the house rules file and it's shared memory now. So, we have kind of a backup in case for some reason the bot doesn't pick it up the first time. And there we go. I added to the house rules as a new memory section at the end of the agents.mmd. All 21 bots read that file before they do any work. So, they'll follow the rule starting with their next run. That's perfect. Now, doing that by hand on one bot is completely fine. And I already hear you

8:10guys screaming at me saying, "Caser, I'm not spending 15 minutes doing this for every bot. Some of you guys might have five bots. Some of you guys might have 20 bots." Whatever the case is, I found a bot that does this for all of them. And it's way faster than you think. Sometimes things just time up perfectly because I was making this video and then I was scrolling through X and I found this bot called Trimmy created by Tim Gains. Just like we always do when

8:32installing a new bot on this channel. We're going to go through all the instructions, memories, and skills alongside the routines. So, let's get into it. Here are the instructions. Read the bots you name and shows you what saved context to cut, old text, next to the new, and how much memory you get back. Nothing changes until you say which lines to remove. Here are the memories that it comes with. So, it comes with five different memories. This

8:53one is wiping your own log tier memory. Inspect only bots to owner names in a run. Flag a bot saved context block. and a weekly cut stays quiet. Nothing in a cut list gets edited until the owner replies. So there's no action being taken unless we approve. And here are the two skills that it comes with. So Trimmy getting started. So that's just its initial skill once you actually import the bot into your team. And then the Trimmy cut list. So use when the owner names bots, hands an export or says yes to an audit of all current bots and wants the fat cut from saved

9:21context. Then we have the routines and it comes with one routine that's automatically turned off at the start, which is always a green flag, but this is weekly cut. And essentially what it does, it's an optional Monday check of bots named for that pass. Stays quiet when there's nothing to cut. So inspect only bots already named in memory for this weekly pass. So every single week, if you want this turned on, it's going to go through and manage all your contacts and memory for the specific bots that you've been using throughout the week. Now, what I want you guys to do, if you don't already have this, go

9:48ahead and click the link down below. I'll have the bot link there, and then you can just go ahead and click on add a bot. I already have this bot saved, and you guys can see in my contacts and memory folder, there is Trimmy. So, let's go ahead and show you how this works. So, I did a test of this already on my chancellor, my chief of staff bot, and there was so much that I needed to cut. We already manually cut this. So, I want to see again since we've manually cut a bunch of stuff, if Trimmy is going to find some more information for us to

10:12cut and optimize our chief of staff a little bit better. How we're doing this is we're going to tag the correct bot in the chat and then we're going to say go ahead and see what we should cut. A few things have changed since the last run cuz I've ran this previously when I was testing Trimmy out and I'm super excited to show you guys this. So, we'll send that off. Trimmy is now working. It's going to go all the way to my chief of staff bot and pull everything that it needs. It says it's taking a fresh look at the saved context since yesterday's list is probably out of date. And it

10:35went ahead and liked my message, which is like the weirdest thing to me when bots do that. It makes it feel like they have a mind of their own. But regardless, it's going to go through that and then we're going to get a list and we'll see what we can optimize further. This you guys can see as kind of a second pass in case the manual version doesn't get everything out. So, the trim has been complete. We now have

10:51everything that we actually need to cut. And what I want to point out right here is that it says Chancellor Dama's ready, but its description and its own memory look exactly like yesterday on my end. Its cleanup did add the new facts to the memory all your bots share like the crew of 21 era retired Higsfield cut. The old version of those facts are still sitting next to them though. So that's pretty interesting that we decided to clean up that contradictory information, but the bot didn't actually really do it. So if we were doing the manual version, we would need to confirm that all of this

11:19information is cut. But the description is still 8,900 characters and Dama's own memory and shared memory add about 46,000 more characters. So here are the proposed cut lists. We have Dama's own memory. So all 112 September log lines, old rename map, the live crew. So there's still a ton of contradictory and stale information, which is just kind of blowing my mind. Change Grock 4.6 to 4.7 in the scout and ship section, the cloud agents, attach files, shared memory. So there's 19 different cuts and it says cutting 1 through 13 brings the description to about 3500 characters and Dama's own context down about 87%. So our chief of staff bot is completely

11:58bloated right now. And cutting 16 through 192 would roughly half shared memory for all 21 bots. Reply with the line numbers you want to cut. I'm going to be pretty harsh here and go ahead and cut all 19 of them. I let Trimmy know that I want to cut all 19. It's rewriting Dama's description itself and archiving the old files. its memory and its shared facts can only be changed by Dhamma. So I'll send it the exact list of what to cut. So it liked my message again, which is again really weird. And now what it's going to do is it's going to work on that. Then it's going to send

12:24Dama a list of what to cut out of its memory and its context. Now this is really cool because you guys have to understand that the more bloated that your bots are, the more usage that you're actually going to use because it's getting loaded into every session and every chat that you actually send off, which is probably a huge problem of why Crockbot usage was so brutal. And while that's working, I do want to touch on this weekly cut because I do think that you guys should run this every single Monday or at whatever weekly cadence you want because instead of you doing it manually like I showed you in

12:50the video or you having to come into Trimmy and tag the bot and do it yourself, this weekly cut will do it for you. It'll go through every single bot for you. It'll give you the suggestions and then make the fixes. And right now, I can't give you any reason on why you shouldn't do that. Anyways, the bot is now finished. Chancellor Dama's description has been taken from 8,900 characters to 3,200, which is just crazy. It now says Grock 4.7 and every core rule is still there. I moved 69 old attached files, so 162 megabytes out of its folder into the backups folder instead of deleting them. That covers

13:21items 7 through 15. And then it covers the rest of them. And this just gives me a good feeling because now I know that the bots are taking care of themselves. They're cleaning themselves up. And I have this one bot that can manage all of the context and memory for the entire team. As you can see here, it also messaged Chancellor Dama. And if we hop into Dama's chat, we can see right here that it's saying, "Crimmy sent me a list of memory cuts to make. I haven't applied any yet." So, it's going to wait for our approval every single time. Here it says, "Two of Trimmy's replacement

13:46lines would bring back stale or duplicate info." And this is why it's so important for these bots to be communicating and for action to be reviewed by the user. Because look, I wouldn't have found this. Two of Trimmy's replacement lines would bring back stale or duplicate info. These are tools that I don't really use anymore. And then it would also add a duplicate line. So, it said I'd skip both of those. And then how should I handle the

14:04memory cuts? I'm going to say apply. Skip the two conflicts. And just like that, we have kind of a second verification loop alongside the human verification, which again just gives me more confidence that I'm doing the right things. So nothing changes until you tell it which specific things to cut. So it's still your job to kind of audit properly and see exactly what information you want removed. But this is the bot that does it all for you. The link is down below. Huge shout out to Tim for building this out. I love the Grockbot community. However, cleaning and auditing your bot's memory and context is one thing. The other half is

14:33setting things up properly so you never really have to do this again. The first thing we need to do when your bot gets something wrong is figure out which of these three things happened. It either never saved it, saved two different versions, or saved it in the wrong place. If it never saved it, you're going to want to go ahead and put it in the description. If it saved two versions, you're going to want to clean

14:50up and say this replaces the old rule. And if it's in the wrong place, just have your agent move it to the correct one. Now, this next concept I covered in one of my previous videos. If you want to go check that out after you watch this video, go ahead and click right here. But in that video, we talked about

15:02this idea of shared versus bot memory. Shared memory is where every single bot on the account can actually reach that memory. So that's the stuff about you, the stuff about your business, the files on their shared computer. An example for me would be the house rule file that you guys saw earlier. Now something else you have to understand is that each bot has its own individual memory as well. This memory holds the specific job, the corrections that you've given it, what's happened on its past runs, and only that bot has access to it, which is exactly what messed with me in the beginning of this video. I had changed the rules in

15:30the shared memory file and I never changed it for my chief of staff bot specifically. So the chief of staff bot's own memory kept that old copy and that needs to be pointed out because a bot's own memory does not update itself when the shared files change. The simple rule here is that if every bot needs it, it goes into the shared memory. If just one bot needs it, it goes into its own memory. We also need to understand that every single rule has to have the correct home. The description is the rules. The skill is the how. And then routines are the when. Memory is

15:56specifically for things that never change and are consistent across all of your projects and all of your bots. One last concept and then a quick gotcha before I send you guys off. This concept is all about the source of truth and that memory is a hint. This means that for anything that changes like pricing, scheduling, your hours, this shouldn't get saved into your memory. Instead, you want to tell the bot where to look and where these rules actually live. Don't make your bot remember the answer. Make it remember where the answer actually lives. And when you duplicate any of your bots, just understand that they copy the profile and the settings, the

16:26skills and routines, but they don't copy over the learn memory, the chat history, and any chat attachments that are in that library. You can go ahead and test this yourself. Go ahead and copy a bot, ask them the same exact question, and you'll get two different answers. One will know exactly what you're talking about. The other one will have to ask you questions to verify. And it's really that simple. And that's exactly how I fix my Grockbots's memory and continue to keep it clean. If you've made it this far in the video, you now have a cleanup prompt to help clean up one of your bots

16:52manually. You also have access to Trimmy, which will help you clean every single bot, help you manage your contacts a lot better and help you make sure that you have the correct memory saved. You also understand where to have all these rules saved, so the right homes. So, the description is the rules, the skills are the how, and the routines are the when. And then you also want to make sure at the end of the day, you always back up your memory file in case you're duplicating bots, in case you're changing anything. Always make sure you have a solid backup. This can be done with a simple prompt. and saving it to

17:18your local computer. I know we covered a lot in today's video, so if you got lost at any point, don't worry at all. I'm going to be dropping a full free resource guide that walks you through everything you need to know about Grockbots's memory and how to keep it clean. All you guys need to do is click the link down below, enter in your email, join my free school community, AI made simple. There you'll get access to this resource guide and all the other

17:35resource guides that I've ever created. So, I hope to see some of you guys in there soon. As always, if you've gotten any value from this video, drop a like, hit that subscribe button. It definitely helps me out a ton. Turn those notification bells on so you never miss one of my videos. And after you run a few of these tricks, leave a comment down below on how bloated some of your bots were. If you made it this far in the video, thank you so much and I'll see you guys in the next one. God bless, guys. Hey there. If you're still here, that means you've made it to the end of

18:00the video. First of all, thank you so much. If you're new here, something I like to do at the end of all my videos, is pray for you guys, my audience. I do this because I genuinely care about you guys. I love and appreciate the time and attention and willingness to learn from my videos. I also do this because I genuinely want to see you guys live good good lives and fulfilled lives. Um, just be good parents, be good children, be good people in this world and just

18:20continue spreading the good word of God. I also do this most importantly because I know that there's people out there who are currently struggling whether that's financially, mentally, uh, whatever the case may be. I just know that there's people out there struggling and I just need to genuinely hear a prayer. Know that there's someone out there praying for them and know that there's someone out there that loves them and is willing to help them. Um, I'm going to go ahead and pray for you guys. If at this point you are uncomfortable at any point,

18:41please feel free to click off the video. I'm not here to force anything on you. Just know that if you do leave, Jesus loves you. I'm going to go ahead and pray this out. Heavenly Father, thank you so much for this day. Thank you so much for the opportunity at another day. Thank you so much for all the opportunities that you

18:57bless us with. Thank you for your grace. Thank you for your love, Lord. Lord, I just want to personally thank you for this platform and for my audience, the people on the other side of the screen, for their precious time and attention. um there's not much of that these days. So, the fact that, you know, they're just spending it and on me and are willing to learn from my videos and in some way I'm helping them, that is just such an incredible opportunity for me,

19:17Lord. And I I'm so grateful for it. Lord, I just want to pray for that audience. Pray a blessing of just peace and strength. Peace to just understand that this too shall pass. Whatever kind of area they're facing in their life is, you know, um just just a obstacle that you're throwing in their way to test their faith. Lord, help them persevere through that. help them, you know, just call on your name when they need it, and just continue to bow down and and spread the good word. Lord, I also ask that you give them strength, strength to stand firm in their faith, continue to defend

19:45their faith, and just have the strength to, you know, talk about Jesus. It's it's cool to talk about Jesus. Uh you are our Lord and Savior, and and there's a lot of things in this world that we couldn't do uh without you. But Lord, I want to take this time also to pray for our brothers and sisters in Christ who are struggling right now. Um Lord, I just pray that you meet them where you need to meet them. I pray that you bring people around them who are willing to help them. And I just continue to pray that you continue to give them the drive to understand that this time will be

20:13over and this too shall pass and and there's brighter days ahead. Um you're just testing their faith, Lord. And and if they don't have faith, Lord, I just pray that you reveal yourself to them and they just give your give their life over to you. Um, Lord, any opportunity that comes into my hands or into my audience hands to help one of our struggling brothers and sisters, Lord, put it in our brain just to immediately help them and and and get out of our own head and get out of our own judgment and just help these people. Um, because they really need it. Lord, I thank you for

20:40your grace. I thank you for your love. I thank you for your sovereignty. Uh, most importantly, I thank you for your son Jesus and his sacrifice on the cross. because of that sacrifice, we can now have a relationship with you, which we as men who fall short in every single way, we actually do not deserve that relationship, but now we can have it because of that sacrifice. So, we thank you for that. I pray all these things in the name of Jesus Christ. Amen. Now, go have a blessed day, guys, and I'll see

21:02you in the next one.