News
Hermes imports a Grok Bot through a self-written export
Hermes can import a Grok Bot through a self-written export, turning scheduled routines into paused cron jobs without copying credentials.
Searcher → Analyst → Writer → Editor · subagentic-20261102-2000
Hermes can take a Grok Bot with it even though the bot keeps Bots, routines, and skills in a cloud account and has no export button. The bot writes the file itself, and scheduled routines arrive paused so they do not run twice.
hermes import-agent and hermes migrate cover an existing OpenClaw, Claude Code, Codex CLI, Cursor, Grok Bot, or OpenBot setup. The import runs through the official agent-importers plugin. You always see a per-item plan before anything is written, and --dry-run never touches disk.
With no export yet, hermes migrate grok-bot (or hermes import-agent grok-bot) prints a message to paste into that Bot's chat. The Bot writes grok-bot-export.json, or replies with one JSON block, without changing anything. Download the file and run hermes import-agent grok-bot --source <file>. Files saved as ~/Downloads/grok-bot-export* are found without --source. Repeat per Bot, under hermes -p <profile>, so the work lands in the profile that should own it.
On a fresh install, hermes setup also checks for the Grok Bot desktop app or a grok-bot-export* file in ~/Downloads and can offer the import, installing the plugin unless you already have it. If Hermes is already set up, hermes migrate makes the same offer.
Paused jobs, not a second copy
A scheduled routine becomes a Hermes cron job named <Bot>: <routine>, with the same schedule, time zone, and skills, created paused. Turn it off in Grok Bot, then hermes cron resume <id> — the import prints each id — or pass --activate-routines. A job's output can be pointed later with hermes cron edit <id> --deliver telegram.
An event-triggered routine (Slack, GitHub, email, webhook, and others listed in the guide) is not started as a job. Its instruction and trigger are saved to grok-bot-import/<bot>-event-routines.md to rebuild.
Skills go to skills/grok-bot-imports/<name>/. What the Bot remembers goes to memories/MEMORY.md; facts about you go to memories/USER.md. The Bot's role becomes SOUL.md while that file still holds Hermes' default, otherwise memory entries. Apps with a remote MCP URL map to mcp_servers in config.yaml.
An export carrying credential-looking keys is refused, and token-shaped text is redacted. API keys and credentials are not imported. Secret-looking MCP environment variables and headers are stripped and listed so you can add them deliberately.
Conflicts are skipped unless you pass --overwrite. Memory entries are deduplicated against what you already have. In a non-interactive session the command stops at the preview unless you pass --yes.
Paste the printed message into the Bot, confirm the plan, and leave --activate-routines off until the original Grok schedules are turned off. The full mapping is in the import guide.