Most Expensive Grok Bot Mistakes (And How To Avoid Them)

0:00I know everyone's been talking about how great Grockbot is, but how about we take a look at what's not great instead. So, today I'm going to walk you through what I believe to be the top three worst parts about Grockbot and even give you some solutions to make these problems more bearable. Starting off with probably every AI user's worst nightmare, accidental token leaks. Yeah, I said token leaks. Let me explain. Say you've got a manager bot like mine or a chief of staff whose whole job is coordinating a bunch of other bots for you. When you tell it to give some of your other bots a job, your manager can

0:32actually DM the other bots and start conversations with them. Each of those simple chats between bots wakes up its own working context window. One for bot one, one for bot two, and one for bot 3. And obviously, your AI tokens are used to process the information inside of each and every one of those context windows. And the longer those windows build up over time with more messages and info, the more tokens are used up to process the majority of those fat threads. So, instead of just one bot burning tokens, processing its own context, you're paying for your chief of staff's context, plus the context of every conversation the chief has had

1:06with the other bots you told it to address, all for one task. And if those other bots start messaging each other on top of that, well, be prepared to keep an eye on your weekly limit. Sure, the context conversation compacts and shrinks over time, but not nearly enough to make opening that many threads cheap. But thankfully, there are ways you can at least prevent that many windows from being processed in the first place. Now, while there's no direct way to clear a bot's conversation context, you can at least get a brand new window if you make a separate channel for that bot to chat in. And whenever that channel

1:36conversation runs a little long, you can just start a new one and then either delete or even archive the previous chat. This is especially effective with groups of bots where you can set a standing rule for bots to simply not DM each other constantly, but instead converse only inside of their respective channels. And hey, asking your manager to be token efficient and aware of heavy tasks isn't a bad idea either. And all that was just dealing with tokens. The second issue you'll run into with Grockbot can get you into some hot water regarding the terms and services of certain online platforms and even lead to accidental account bans if you aren't

2:08too careful. Again, let me explain. Every Grockbot account gets its own cloud computer for the bots to work with. And each bot gets access to its own unique desktop that comes with a browser. it can log into an actual website the same way you would click around and pull up whatever it actually needs because that's exactly where things can go completely backwards if you aren't careful because using bots to poke around websites can uh definitely run into some problems. A lot of platforms flat out don't want data scraping bot accounts let alone any automated access near their sites period. But the thing is it's not really

2:41about whether the bot means well or not. a bot logged into your account, clicking through pages and pulling data over and over. That starts to look a whole lot like automated harvesting, even if all you actually wanted was one number off of the dashboard. And that's the kind of behavior a lot of these sites are actively built to detect and shut down, especially at the beginning of the AI era. So, the actual fix comes down to

3:02using the right door for the right job. Whenever a platform's got an official API or supports something like OOTH, use that instead of a raw login since it's sanctioned access instead of a bot simply pretending to be you. And same goes with any of the built-in connectors Grockbot offers and only grants what it actually needs because read only for stats looks very different from a login that can easily upload, edit, or publish on your behalf, which is easily pushing banan territory in some cases. And if a site's terms explicitly say no bots are scraping, don't even try to pull a fast one on your main account anyways. A

3:34general rule of thumb is to keep your important accounts tied to anything you truly care about away from anything risky or experimental, which shouldn't be too hard as you kind of can only log into one account per platform on the Grobbox computer anyways. And that's effectively the third issue, which I'll admit might be cheating a bit as it's a bit of a trade-off rather than a flatout problem. But hear me out. Each bot gets its own desktop within the cloud computer, sure, but the files on that machine, a lot of the tools, and any browser login you signed into all stick around for the whole crew. Just so

4:05handing off browser tasks from one bot to another is as smooth as possible. But that same convenience can also be the problem because if you had a bot log into say a Discord account to handle some Discord things, that would mean the whole cloud computer is now logged into that specific Discord account. So, if you've got separate bots meant to handle separate Discord accounts, you can't

4:24actually have both signed in at once. One login just replaces the other. The solution to this is that there's no direct solution. You could constantly just log out and back into swap, but then you're potentially dealing with passwords and 2FA every single time and just completely forget about having two bots on the same platform using different login. What actually matters is just deciding what belongs on the machine in the first place and only leave logged in what you'd be fine with the whole team touching. It's still a very impressive tool, but learning the ins and outs of how it works can definitely help prevent yourself from

4:55running into these kinds of situations in the first place. So, if you're already building out a team of your own, let me know down in the comments if any of these have gotten to you or if you found smarter ways around them. If you made it this far, thanks again for sticking around. And oh, if you feel like watching arguably the best top five Grockot features for a change of pace, feel free to watch this video also by

5:16me.