You can now migrate Grok Bot to Hermes with one command. Nous Research added a Grok Bot importer to its official Agent Importers plugin on 2 November 2026, the same day Hermes v0.22.6 shipped with hermes migrate and setup able to move Grok Bot users over. Your scheduled routines become Hermes cron jobs, your skills become Hermes skills, and what your Bot remembers becomes Hermes memory. Below is the exact flow, what comes over, what you rebuild by hand, and how to switch without anything running twice. My video is right under this intro.
Key takeaways
- Run
hermes migrate grok-bot(orhermes import-agent grok-bot). - Grok Bot has no export button, so each Bot exports itself from a prompt Hermes gives you.
- Scheduled routines become cron jobs, created paused so nothing runs twice.
- Logins and API keys are never imported; connected apps stay in Grok Bot.
- Want help moving your business agents over? Claim a free strategy session.
What the Grok Bot importer is
The importer is part of the agent-importers plugin in Hermes Official Plugins (version 1.2.1, which needs Hermes 0.21.6 or newer). The same command already brought over OpenClaw, Claude Code, Codex CLI and Cursor setups. Grok Bot and OpenBot were added on 2 November.
Every run shows a per-item preview before it writes anything, and --dry-run never touches disk. API keys and credentials are never imported.
Step 1: start the migration
hermes migrate grok-botPer the Hermes CLI reference, hermes migrate grok-bot installs the agent-importers plugin from the catalog if it’s missing, then runs hermes import-agent grok-bot. A bare hermes migrate looks for Grok Bot (the desktop app or a grok-bot-export* file in Downloads) and other agents on your computer and offers to import what it finds. A first hermes setup runs the same check.
With no export yet, Hermes prints a message for you to paste into Grok Bot. It also saves it as grok-bot-import/export-prompt.txt in your Hermes home.
Want your AI agents moved over and running for your business? Inside the AI Profit Boardroom you get the Agent OS — Hermes, OpenClaw, OpenCode, Claude and Codex in one place — plus step-by-step Hermes training and four live coaching calls a week.
Want a plan for your business first? Claim your free strategy session.
Join the AI Profit Boardroom →Claim Your Free SEO Strategy Session →
Step 2: let each Bot export itself
Grok Bot keeps your Bots, routines and skills in its cloud account and has no export button. So, per the README:
- Paste the message into a Bot’s chat. The Bot writes
grok-bot-export.jsonand attaches it, or replies with one JSON code block. Nothing in Grok Bot changes. - Repeat for each Bot you want to move.
- A long export can come in several parts; they’re merged per Bot, and a part sent twice adds nothing.
If the Grok Bot desktop app is on the same computer, the importer reads its local cache (Bot names and recent routine names, never its login files) to list your Bots and flag a routine a Bot left out of its export.
Step 3: import the file
hermes import-agent grok-bot --source ~/Downloads/grok-bot-export.json- Files saved as
~/Downloads/grok-bot-export*are found without--source. --sourcealso takes a folder of exports.- On a Mac you can pipe a copied reply straight in:
pbpaste | hermes import-agent grok-bot --source - -y. --bot <name>imports only one Bot from an export holding several.- Run it into the profile that should own that Bot’s work:
hermes -p <profile> import-agent grok-bot --source <file>.
Easier option: ask Hermes, “Run hermes migrate grok-bot, give me the export prompt, then import the file from my Downloads folder with a dry run first.”
What comes over (and what doesn’t)
| In Grok Bot | In Hermes |
|---|---|
| Routine on a schedule | Cron job with the same schedule, time zone and skills, created paused |
| Routine on an event (Slack, GitHub, email, webhook…) | Not scheduled; its instruction and trigger are saved to a file for you to rebuild |
| Skills | skills/grok-bot-imports/<name>/SKILL.md |
| What the Bot remembers | Memory entries in memories/MEMORY.md |
| Facts about you | memories/USER.md |
| The Bot’s role and lasting rules | SOUL.md if it still holds Hermes’ default, otherwise memory |
| Apps with a remote MCP URL | mcp_servers in config.yaml (sign in again in Hermes) |
| Other connected apps | Listed in the report; their logins stay in Grok Bot |
Safety checks: an export that carries credential-looking keys is refused whole, and token-shaped strings inside text are replaced with [redacted].
Want this set up for you instead of doing it yourself? Claim your free strategy session →
Switch over without running things twice
Routines arrive paused because your Grok Bot copy keeps running until you turn it off. Two live copies would do the work twice. The safe order:
- Turn the routine off in Grok Bot.
- Run
hermes cron resume <id>(the import prints each ID). - Choose where results go:
hermes cron edit <id> --deliver telegram(or discord, slack and others).
Or pass --activate-routines to create them running. Re-running the import skips routines whose cron job already exists. More on scheduling in my Hermes Agent cron job guide.
My verdict
If you’ve built routines and skills in Grok Bot and want them in an open-source agent you control, this is the clean path: dry run first, import one Bot at a time into its own profile, rebuild event routines and app logins, then switch routines over one by one. That’s how to migrate Grok Bot to Hermes without losing work.
About Julian Goldie
I’m Julian Goldie — founder of Goldie Agency and the AI Profit Boardroom. I test new AI agents almost every day for 432K+ YouTube subscribers and run Hermes, OpenClaw, OpenCode, Claude and Codex side by side in my own Agent OS. Claim your free strategy session or join the AI Profit Boardroom.
Want another angle? Read the AI Profit Boardroom guide to Migrating Grok Bot to Hermes.
FAQ: migrate grok bot to hermes
How do I migrate Grok Bot to Hermes?
Run hermes migrate grok-bot. Hermes gives you a message to paste into each Bot, the Bot writes an export file, and hermes import-agent grok-bot –source with that file brings it in.
Does Grok Bot have an export button?
No. The importer README says Grok Bot has no export button, so each Bot exports itself from the prompt Hermes prints, as a JSON file or one JSON code block.
Will my Grok Bot routines keep running?
Scheduled routines become Hermes cron jobs created paused. Turn the routine off in Grok Bot, then run hermes cron resume with the ID so the work doesn’t run twice.
Are my logins and API keys imported?
No. Credentials are never imported. Apps with a remote MCP URL become MCP servers you sign in to again, and other connected apps stay in Grok Bot.
What happens to event-triggered routines?
Routines that run on Slack, GitHub, email or webhook events aren’t scheduled. Their full instruction and trigger are saved to a file so you can rebuild them in Hermes.
Does importing change anything in Grok Bot?
No. Writing the export doesn’t change anything in Grok Bot, and every import shows a preview first. Use –dry-run to check without writing to disk.
Ready to put Hermes to work in your business? Join the AI Profit Boardroom for the Agent OS, setup training and daily updates.
Or claim your free strategy session and we’ll map out your setup.
Starting from zero? Get the free AI course and community.
Join the AI Profit Boardroom →Claim Your Free SEO Strategy Session →Get the FREE AI Course + Community →
Related reading
Last updated November 2026. This page is a living guide to migrate grok bot to hermes — the facts here move fast and it is updated as they do.
Done-for-you AI SEO
Rank #1 with AI SEO and get more leads, traffic and sales
Done-for-you SEO packages: backlinks, AI-powered articles and an account manager every month. Save 30% with code BLACKFRIDAY (ends Dec 1). No setup fees.