01What Grok Bot Hermes Agent Migration Is and How It Works

A grok bot hermes agent move means taking the bots you built in Grok Bot and running them inside Hermes instead. Hermes is an open source agent, and it now has a Grok Bot importer built in, so one command and one prompt bring your bot's role, memory, skills and routines across.

In this episode, Julian Goldie shows why he did this and how. Over Halloween weekend, people woke up to find their weekly Grok Bot usage maxed out. So Julian built what he calls a lifeboat and moved his whole bot team over to Hermes.

He built three systems around the move:

  • Lifeboat moves a bot from Grok Bot into Hermes.
  • Fuel gauge shows you where your usage goes.
  • Twin engine keeps your work going when Grok Bot runs dry.

The idea is simple. Your bots keep doing the same jobs. They just live somewhere you control, so a sudden usage cap does not stop your business.

02Why Grok Bot Limits Pushed Bots to Hermes

The trigger was a change in Grok Bot usage limits. TechCrunch reported it on November 2nd. Some Grok Bot users saw their weekly usage jump from 50% to 100%, even when they had not used it overnight.

Elon Musk confirmed on X that it was not a glitch. He has not said what the limits will look like going forward. That leaves anyone who depends on Grok Bot in an awkward spot.

Think about what a business might run on Grok Bot every day:

  • Finding new leads on a schedule.
  • Writing follow-ups.
  • Morning routines that run on their own.
  • Small teams of bots that each handle one job.

If the weekly usage bar fills up early, all of that stops until it resets. You cannot plan around a limit you cannot see coming. That is the problem Julian set out to fix.

Moving to Hermes does not mean throwing your Grok Bot work away. The point of the lifeboat is that the bots you already set up, with their rules and memories, come across in one go. You keep the work you have done and gain a home that does not depend on one weekly cap.

03How the Grok Bot Export Prompt Works

Here is the key thing to know. Grok Bot has no export button. So Hermes takes a clever route.

It gives you a prompt, you paste that prompt into your bot, and the bot packs itself up into one file.

Julian tested this with a bot called lead finder. He gave it three things:

  • A role.
  • The rules for what makes a good lead.
  • A routine called morning leads that runs every weekday at 8.

In the terminal, he ran the Hermes migrate command for Grok Bot. Hermes found the Grok Bot app on his Mac, listed every bot he had, and printed the export prompt.

He pasted that prompt into lead finder. The bot read its own setup and attached one file, a Grok Bot export for lead finder. Julian saved that file to his Downloads folder.

This is the first half of the lifeboat. The bot describes itself, so nothing gets lost in a copy and paste job. You do not have to rewrite its role or its rules by hand.

Once the export file sits in Downloads, Hermes can pick it up and rebuild the bot on its side.

04Importing a Grok Bot Into Hermes Agent Safely

Back in the terminal, Julian ran the Hermes import agent command for Grok Bot with the dry run flag. Hermes found the export file on its own. It then showed him everything it would move before it changed anything.

Once the list looked right, he ran the same command for real. 66 items came across, including:

  • The bot's role.
  • Its memories.
  • The facts it knew about Julian.
  • Every skill.
  • The morning leads routine, set up as a cron job with the same schedule and timezone.

Two things stay behind on purpose. Your API keys never move. You add those yourself in Hermes setup.

And the routine arrives paused, so the same job never runs twice in both places.

Then came the real test. Julian asked Hermes what it knew about his business. It answered with the memories it had in Grok Bot: Bristol, the 40-mile delivery radius, and a named owner for every lead.

Same bot, new home.

The dry run step is worth copying every time. It lets you see exactly what is about to change before anything happens, so there are no surprises.

05Fuel Gauge: See Where Your Bot Usage Goes

The second system is the fuel gauge. It answers a simple question: which bots are eating your usage?

For each bot, it does three things:

  • Takes the real tokens used per run.
  • Multiplies that by how often the routine runs each week.
  • Shows the total against a weekly limit that you set.

When Julian ran it on his team, the result came out deep in the red. The fuel gauge also told him why. Some of his bots were doing the same job.

Lead finder already looks for cafes and offices, so a separate office scout bot was doubling up on work.

So he ran the fuel gauge merge step. It paused the two extra bots without deleting anything. The needle dropped to 45%, back in the green.

This is the part Julian likes most. You stop guessing where your usage goes, because you can see it. If you run a team of bots, overlap is easy to miss.

Two bots might check the same places for the same leads every morning. The fuel gauge turns that hidden waste into a clear number you can act on.

06Twin Engine: Keep Work Running When Grok Bot Runs Dry

The third system is the twin engine. Its job is to keep your work going when Grok Bot runs out of usage.

When Julian ran it, all four bots kicked off in Hermes. Lead finder came back with a fresh table of 10 Bristol cafes, with sources. So the work that would have stalled in Grok Bot carried on in Hermes.

There is a useful lesson in how he built it. He first made twin engine as a skill you talk to. But his model sometimes skipped the skill and did its own thing.

So he turned it into one plain command instead.

That command can only do three things:

  • Resume a job.
  • Run a job.
  • Pause a job.

It never deletes a job. That limit is a safety feature. When a tool can only resume, run or pause, a mistake cannot wipe out your routines.

The wider tip is worth remembering. If a model keeps skipping a skill, a simple command with a short list of allowed actions can be more reliable than asking the model nicely.

07How to Set Up Grok Bot Hermes Agent Step by Step

Here is the full setup from scratch, in the order Julian walks through it in this episode.

  1. Install Hermes. Paste the install line from the Hermes docs into your terminal. Then type hermes to start it.
  2. Pick your model. Hermes works with OpenRouter, OpenAI or your own endpoint, among others. Julian pointed his at GPT OSS running through Ollama.
  3. Run the migrate command. Run the Hermes migrate command for Grok Bot and copy the prompt it prints.
  4. Export each bot. Paste that prompt into each Grok Bot you want to move. Save each export file to your Downloads folder.
  5. Do a dry run. Run the Hermes import agent command for Grok Bot with the dry run flag. Check the list of what will move.
  6. Import for real. Run the same command again without dry run.
  7. Check your routines. Look at your scheduled jobs in Hermes to confirm each routine came across with the right schedule.

After that, add your API keys in Hermes setup, since they never move over. Then turn on the routines you want, because they arrive paused.

08Tips, Limits and Who This Is For

A few points from this episode will save you trouble:

  • Always dry run first. It shows every item before anything changes.
  • Add your API keys by hand. They are left behind on purpose.
  • Unpause routines yourself. They arrive paused so no job runs twice.
  • Use the fuel gauge to find bots that overlap, then pause the extras.
  • Prefer a plain command over a skill when the model keeps ignoring the skill.

This setup is for anyone whose business runs on Grok Bot, such as finding leads or writing follow-ups, and who got caught by the new weekly limits. It suits small teams of bots with set routines, like Julian's lead finder for a Bristol business.

It matters because a usage cap you cannot predict can stop your work without warning. With your bots in Hermes, you can pick your own model, see where your usage goes, and keep jobs running.

Julian shares his exact setups for moving off Grok Bot inside the AI Profit Boardroom. That includes the lifeboat steps, the fuel gauge command and the twin engine command, with scripts, prompts and a short step-by-step guide for each one.