---
title: 'Grok Bot Limits? Move Your Bots to Hermes! 🤯'
source: 'https://youtube.com/watch?v=M532DfwIVnY'
video_id: 'M532DfwIVnY'
date: 2026-11-19
duration_sec: 397
channel: 'Julian Goldie SEO'
---

# Grok Bot Limits? Move Your Bots to Hermes! 🤯

> Source: [Grok Bot Limits? Move Your Bots to Hermes! 🤯](https://youtube.com/watch?v=M532DfwIVnY)

## Summary

The video addresses Grokbot's sudden weekly usage limit increases, which left many users unable to run their bots. The creator demonstrates how to migrate bots to Hermes, an open-source agent from Noös Research, using its built-in Grokbot importer. Three systems are showcased: Lifeboat for migration, Fuel Gauge for usage tracking, and Twin Engine for seamless switching between platforms.

### Key Points

- **Grokbot Usage Limits Hit Users** [00:02] — Users found their weekly Grokbot usage maxed out, even without overnight activity. TechCrunch reported on November 2nd that usage jumped from 50% to 100%. Elon Musk confirmed it wasn't a glitch, leaving future limits uncertain.
- **Hermes Offers Migration Solution** [01:01] — Noös Research released Hermes version 0.22.6 on November 2nd with a command called 'Hermes migrate Grokbot'. Since Grokbot has no export button, Hermes provides a prompt that users paste into their bot to pack it into one file.
- **Lifeboat System: Step-by-Step Migration** [01:30] — The creator demonstrates migrating a bot named 'Lead Finder' for a coffee roaster. Steps include running 'Hermes migrate Grokbot', pasting the export prompt, saving the JSON file, and using 'Hermes import agent Grokbot --dry-run' to preview changes before executing. 66 items transferred, including role, memories, skills, and routines.
- **What Stays Behind on Purpose** [02:27] — API keys never move; they must be added in Hermes setup. Routines arrive paused to prevent duplicate runs. The bot retains its knowledge, such as business details and delivery radius.
- **Fuel Gauge System: Usage Tracking** [03:20] — Hermes saves session token usage locally. The creator built a command that calculates tokens per run, multiplies by weekly frequency, and compares against a set limit. His team used 929,000 tokens against a 750,000 limit (124% over). Merging duplicate bots reduced usage to 45%.
- **Twin Engine System: Seamless Switching** [04:16] — Keeps Grokbot for its strengths while having the same crew ready in Hermes. Commands 'twin engine out' resumes all imported routines and runs them immediately; 'twin engine back' pauses them again. This ensures work continues when Grokbot hits limits.
- **Setup Steps from Scratch** [05:00] — Seven steps: install Hermes, choose a model (e.g., GPT-OSS via Ollama), run migrate command, paste prompt into each Grokbot, import with dry-run then real, check routines with 'Hermes cron list', and add fuel gauge and twin engine commands.

### Conclusion

Migrating to Hermes preserves bot functionality and prevents downtime from Grokbot limits. The three systems—Lifeboat, Fuel Gauge, and Twin Engine—offer a practical, automated approach to managing AI agents across platforms.

## Transcript

weekend, people woke up to find their weekly Grokbot usage maxed [music] out. So, I built a lifeboat and I moved my bot team over to Hermes. Hermes is the open source agent from Noös Research [music] and as of this week, it has a
Grokbot importer built in. One command, [music] one prompt, and your bot's role, memory, skills, and routines come across. I'll show you three systems I built around it. Lifeboat, which moves a bot over, fuel gauge, which shows where
your usage goes, and twin engine, so your work keeps going when Grokbot runs dry. First, what happened? Tech Crunch reported it on November 2nd. Some Grokbot users saw their weekly usage jump from 50% to 100% even when they
hadn't used it overnight. Elon Musk confirmed on X that it wasn't a glitch and he hasn't said what the limits will look like going forward. So, if your business runs on Grokbot, finding leads, writing follow-ups, checking your inbox,
that's a real problem. Your bots stop when the meter hits the top. Noös Research replied the same week. Their answer was simple. Migrated over to Hermes and they shipped it. Hermes version 0.22.6
came out on November 2nd with a command called Hermes migrate Grokbot. Here's the thing to know. Grokbot has no export button. So, Hermes gives you a prompt, you paste it into your bot, and the bot packs itself up into one file. That's
system one. Lifeboat. I made a bot in Grokbot called Lead Finder for a coffee roaster in Bristol. I gave it a role, the rules for a good lead, and a routine called Morning Leads that runs every weekday at 8:00. In the terminal, I type
Hermes migrate Grokbot. Hermes finds the Grokbot app on my Mac, lists every bot I have and prints the export prompt. I paste that prompt into Lead Finder. It reads its own setup and attaches one file, Grokbot export lead finder .json.
I it to my downloads folder. Back in the terminal, I run Hermes import agent terminal, I run Hermes import agent Grokbot with dash-dash dry run. It finds everything it would move before it changes anything. Then I run it for
changes anything. Then I run it for real. 66 items came across. The role, the memories, the facts about me, every skill, and the morning leads routine as a cron job with the same schedule and time zone. Two things stay behind on
purpose. Your API keys never move. You add those in Hermes setup and the routine arrives paused so the same job never runs twice. Then I ask Hermes, what do you know about my business? And it answers with the memories it had in
Grokbot. Bristol, the 40 mile delivery radius, a named owner for every lead. Same bot, new home. If you want my exact setups for moving off Grokbot, like the
lifeboat steps, the fuel gauge command, and the twin engine command from this video, they're inside the AI Profit boardroom. You get the scripts, the prompts, and a short step-by-step guide for each one so you can copy my setup
instead of figuring it out from scratch. Plus the faceless video skill I use to make this video. The link is in the comments and the description or go to aiprofitboardroom.com. System two, fuel gauge. I moved three
more bots over the same way. Cafe Scout, Office Scout, and Review Watch. Now I had a team of four in Hermes. Hermes saves every session on your own machine with how many tokens it used. So I built a small command called fuel gauge that
reads that history. For each bot, it takes the real tokens per run, multiplies by how often the routine runs each week and shows the total against each week and shows the total against the weekly limit I set. 750,000
the weekly limit I set. 750,000 tokens. My team came out at 929,000 124% deep in the red. And it told me why. Lead finder, Cafe Scout, and Office Scout were all doing the same job. Lead
Finder already looks for cafes and offices. So I ran Fuel Gauge Merge. It paused the two extra bots without deleting anything. The needle dropped to 45% back in the green. That's the part I
love. You stop guessing where your usage goes. You can see it. System three, twin engine. Here's the idea. Keep Grok Bot for what it's great at and keep the same crew ready in Hermes. When Grok Bot hits its limit, Hermes picks up the work. The
imported routines sit in Hermes paused. So I built one command, twin engine out. It resumes every routine that came from Grok Bot and runs it straight away. When I ran it, all four bots kicked off in Hermes and Lead Finder came back with a
fresh table of 10 Bristol cafes with sources. When Grok Bot is back, I type twin engine back and every copy pauses again, one command each way. A quick tip
from testing. I first made twin engine as a skill you talk to, but my model sometimes skipped the skill and did its own thing. So I turned it into one plain command that only resumes, runs, or pauses. It never deletes a job. Now
let's set it up from scratch step by step. Step one, install Hermes. Paste the install line from the Hermes docs into your terminal, then type Hermes. Step two, pick your model. Hermes works with News Portal, Open Router, Open AI,
or your own endpoint. I pointed mine at GPT OSS through Ollama. Step three, run Hermes migrate Grok Bot and copy the prompt it prints. Step four, paste that
prompt into each Grok Bot you want to move and save each export file to move and save each export file to downloads. Step five, run Hermes import agent Grok Bot with dash dash dry run. Check the list, then run it again
without dry run. Step six, check your routines with Hermes cron list. They arrive paused. Turn a routine off in Grok Bot before you turn it on in Grok Bot before you turn it on in Hermes, so it never runs twice. And step
seven, add fuel gauge and twin engine so you can see your usage and switch engines with one command. That's it. Your bots keep their role, their memory, and their routines, and your lead finding never stops. If you want the
lifeboat steps, the fuel gauge command, and the twin engine command, they're inside the AI Profit Boardroom with a step-by-step guide for each. The link is in the comments and the description, or go to aiprofitboardroom.com.
go to aiprofitboardroom.com. See you in the next one.
