The tool you use to migrate Grok Bot to Hermes earns an 8 out of 10 from me: excellent on safety and schedules, weaker on event triggers and app logins.
It arrived with Hermes v0.22.6 on 2 November 2026, inside the official agent-importers plugin.
This verdict scores it criterion by criterion from the published docs, then tells you who should use it now and who should wait.
If you want a second opinion on your own setup, book a free SEO strategy session.
The Scorecard
Ratings are my editorial judgement from the Hermes import guide and the plugin README.
| Criterion | Score | Why |
|---|---|---|
| Getting started | 9/10 | hermes migrate grok-bot installs the plugin if missing and prints the export prompt |
| Safety of the run | 10/10 | Preview always, --dry-run writes nothing, and nothing in Grok Bot changes |
| Scheduled routines | 9/10 | Same cron expression, time zone and skills, created paused |
| Skills and memory | 8/10 | Skills, memory, user facts and the Bot's role all get a home |
| Many Bots at once | 8/10 | --bot, folder sources and per-profile runs with -p |
| Re-run behaviour | 8/10 | Existing cron jobs are skipped and duplicate export parts add nothing |
| Event-triggered routines | 5/10 | Saved to a notes file to rebuild, not recreated |
| Connected apps | 5/10 | Remote-MCP apps move but need a fresh sign-in; the rest stay behind |
| Ongoing sync | 4/10 | Grok exports are one-off files and sit outside --sync |
| Overall | 8/10 | Strong first move, with manual follow-up for triggers and logins |
How The Export Works, And Why It's Built That Way
Grok Bot stores Bots, routines and skills in its cloud account, and it has no export button.
The importer's answer is to have each Bot export itself.
Hermes prints a prompt, and saves a copy as grok-bot-import/export-prompt.txt, which you paste into a Bot's chat.
The Bot writes grok-bot-export.json and attaches it, or replies with a single JSON code block.
I rate this design highly because it reads only what the Bot reports and leaves Grok Bot untouched.
The cost is a manual paste per Bot.
For a roster of three that's nothing; for twenty it's a chore, though a predictable one.
Getting the file back into Hermes
Files saved as ~/Downloads/grok-bot-export* are found without any flag, which removes the most common friction point.
Anything saved elsewhere goes in with --source <file>.
A reply that came back as text can be piped in from the clipboard with pbpaste | hermes import-agent grok-bot --source - -y.
Long exports that arrive in several parts are merged per Bot, and a repeated part is ignored.
I'd call that the right amount of forgiveness for a process that involves a human copying and pasting.
The front door
The first-run experience scores well too.
On a fresh install, hermes setup checks for the Grok Bot desktop app or an export file in Downloads before anything else, then offers the import.
Already set up, a bare hermes migrate makes the same offer, and hermes migrate grok-bot goes straight to it.
Strength 1: The Safety Defaults Are Right
Every run prints a per-item plan before it writes.
Non-interactive runs stop at that preview unless you add --yes.
Imported routines are created paused, because the Grok copy would otherwise keep running alongside them.
An export carrying credential-looking keys is refused whole, and token-shaped strings in text are replaced with [redacted].
Before merging memory, the importer backs up MEMORY.md with a timestamp.
That's five separate guards, and I'd struggle to name a missing one.
Strength 2: Scheduled Work Survives Intact
A scheduled routine becomes a Hermes cron job named <Bot>: <routine>.
It keeps the same cron expression, time zone and skills.
You switch it on with hermes cron resume <id> once you've paused the original, and route output with hermes cron edit <id> --deliver telegram.
For most people, scheduled routines are the bulk of the value in a Bot, so this is where the tool scores best.
The paused default is the detail that earns the score.
If you'd rather accept the overlap, --activate-routines creates the jobs running, but the docs make the trade-off plain: two live copies do the work twice.
I'd keep the default and switch each job on by hand after its Grok twin is paused.
Output stays in Hermes until you choose a destination, so nothing gets posted anywhere by surprise on day one.
Strength 3: It Respects How People Organise Bots
The README says to run the import once per Bot into the profile that should own its work.
That maps a roster of single-job Bots onto Hermes profiles cleanly.
--bot <name> narrows a multi-Bot export, and the flag repeats.
--source accepts a file, a folder of exports, or - for a pasted reply on stdin.
A bonus: you pick the model afterwards
The Grok Bot FAQ says Grok Bot chooses the backend model per task and offers no picker.
After the move, each Hermes profile runs whatever provider and model you set with hermes model.
That isn't a feature of the importer, but it's one of the practical differences you'll notice in week one.
🔥 Want the trainings that go with a clean Hermes setup? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS built on Hermes, four coaching calls a week and 3,400+ members who've already moved their agents over. → Join the AI Profit Boardroom
Limit 1: Event Routines Need Rebuilding
Routines triggered by Slack, GitHub, Linear, Sentry, PagerDuty, email or a webhook aren't scheduled in Hermes.
Their full instruction and trigger go to grok-bot-import/<bot>-event-routines.md.
That's honest, since the trigger plumbing differs between the two products, but it's real work for anyone whose Bots mostly react to events.
This is the main reason the overall score isn't higher.
The notes file does keep the full instruction, so nothing is lost; you simply recreate the trigger on the Hermes side.
Teams with one or two triggered routines will barely notice, while a Bot built entirely around Slack mentions will take real effort.
Limit 2: Logins Stay In Grok Bot
Apps with a remote MCP URL land in mcp_servers in config.yaml, and you sign in again.
Other connected apps are only listed in the report, and their logins stay in Grok Bot.
I'd score this as correct behaviour that still costs time.
Nobody should want credentials flowing through an export file.
Model providers are configured with hermes setup, and any app secrets go into the profile's .env.
Expect one focused session per Bot to reconnect what it needs.
Limit 3: It's A One-Off, Not A Bridge
The same plugin offers hermes import-agent --sync for Claude Code, Codex CLI and Cursor folders.
Grok exports aren't part of it, because they're files a Bot writes on request.
If you plan to keep changing a Bot in Grok Bot after you import it, you'll be exporting again.
Re-running is safe, since routines whose cron job already exists are skipped.
That makes a second export a cheap top-up rather than a risky overwrite.
Skills and MCP servers that already exist by name are reported as conflicts and skipped unless you add --overwrite, so your own edits survive a re-run by default.
The Desktop App Cache: A Useful Extra
When the Grok Bot desktop app sits on the same computer, the importer reads its local cache.
It takes Bot names, plus routine names from recent chats, and never its login files.
It uses them to list which Bots to export and to flag a routine a Bot created but left out.
The README notes the app keeps no routine schedules, skills or memory locally, so this cache can check an export but can't replace one.
Who Should Use It Now
- Anyone whose Bots mostly run on schedules.
- Agencies and teams that want one Hermes profile per Bot or per client.
- People who want memory and skills as files they can read and edit.
- Anyone already on Hermes v0.22.6 through the CLI, Docker or the Microsoft Store app.
For these readers the tool does most of the work, and the remaining steps are switches rather than rebuilds.
Who Should Wait
- Teams whose Bots are mostly Slack, email or webhook triggered, until someone has time to rebuild them.
- Desktop-only users on the .exe or .dmg installer, who get v0.22.6 with the next bundled release according to the release notes.
- Anyone who expects a live, two-way link between the products.
Waiting costs nothing here, because the export can be run any time and never changes the Bot.
📞 Want a verdict on your own Bots before you move them? Book a free SEO strategy session and my team will go through which of your Bots score well for a move and which should stay. → Book a free call
How It Compares With The Other Importers
OpenBot, the other desktop app added in the same release, is read directly from its local database, so no paste is needed.
Claude Code, Codex CLI and Cursor are read from their folders on disk.
Grok Bot is the only source where the Bot has to write its own export, which explains both the extra step and the safety of it.
For the folder-based imports and their sync mode, see my Hermes import agent review.
What Neither Product Changes
Grok Bot keeps working exactly as before throughout.
Routines in Grok Bot can be paused from the Bot's details or by right-click, per the routines docs, and pausing is reversible where deleting isn't.
The export file is ordinary JSON, a format Grok Bot handles as a file type, per its files docs.
So the worst case of trying the importer is a JSON file you don't use.
That low downside is why I score safety at the top of the table.
Final Verdict
Use it.
The importer makes the low-risk part of a migration genuinely low risk: preview, paused jobs, refused credentials, untouched source.
Scheduled routines, skills and memory come over in one pass, which covers the work most Bots actually do day to day.
Budget extra time only if your Bots depend on event triggers or many app logins.
For the Agent OS trainings that sit on top of Hermes, join the AI Profit Boardroom.
Also On Our Network
- 🌐 The six-step operator run from export prompt to resumed cron jobs
- 🌐 Whether a small business should move its Bots, and which one goes first
- 🌐 Five copy-paste prompts that let your agent run the Grok Bot import
- 🌐 Which AI model each imported Bot should run, by real GoldieBench scores
- 🌐 The complete Grok Bot to Hermes migration guide on the AI Profit Boardroom blog
FAQ: Migrate Grok Bot To Hermes Verdict
What score does the Grok Bot importer get overall?
8 out of 10. It is excellent on safety and scheduled routines, and weaker on event-triggered routines, app logins and ongoing sync.
What is the weakest part of the importer?
Event-triggered routines. They are written to a notes file to rebuild in Hermes rather than recreated automatically.
Is it risky to try the importer?
No. The export leaves Grok Bot unchanged, every run previews first, and --dry-run writes nothing.
Does the importer keep Grok Bot and Hermes in sync?
No. Grok exports are one-off files and are not part of hermes import-agent --sync. Re-run the export and import if a Bot changes.
Who should wait before moving?
Teams whose Bots mostly react to Slack, email or webhooks, and Desktop installer users waiting on the next bundled release.
📺 Video notes + links to the tools 👉
🎥 Learn how I make these videos 👉
🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉
About Julian
I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
- I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
- I've grown a YouTube channel to 400,000+ subscribers.
- I wrote "Link Building Mastery".
- My Udemy courses have taught over 29,000 students.
→ Get my best AI training inside the AI Profit Boardroom
Score your own Bots against the table above, start with the scheduled ones, and book a free strategy session if you want help deciding when to migrate Grok Bot to Hermes.
