Move your Claude Code, Codex, Cursor or OpenClaw setup into Hermes with a dry run first
by PaperChaseWebb
Nous Research's agent-importers plugin gives Hermes one command that reads an existing agent setup (instructions, memories, MCP servers, skills and command allow and deny lists) and shows a per-item plan before writing anything. Credentials stay behind unless you opt in for OpenClaw.
- Price
- Free
- Difficulty
- Beginner
- Setup
- 15 min
- Format
- .md file
move-your-claude-code-codex-cursor-or-openclaw-setup-into-hermes-with-a-dry-run-first.md · 3 KB · direct download, no signup
What you end up with
The dry run and the skip-on-conflict default are what make this safe to try.
What you get
- A plain-language summary of the workflow
- A fill-in prompt template
- What to watch out for
- A link to the original source
Who it is for
Builders who already use AI agents and want a proven workflow they can copy into their own project.
Works with
Solid chips: the agent is named in this listing's own tools list. Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.
Tools needed
Cost to run: Free with the agent plan you already use.
Time to result: One working session
How it works
Install the plugin: hermes plugins install agent-importers
Install the plugin: hermes plugins install agent-importers.
Expected: Done before you move to the next step.
Preview: hermes import-agent claude-code --dry-run (or codex, cursor,
Preview: hermes import-agent claude-code --dry-run (or codex, cursor, openclaw).
Expected: Done before you move to the next step.
Read the per-item plan, especially MCP servers and command allow lists
Read the per-item plan, especially MCP servers and command allow lists.
Expected: Done before you move to the next step.
Apply without --overwrite so existing Hermes items are kept
Apply without --overwrite so existing Hermes items are kept.
Expected: Done before you move to the next step.
Set API keys fresh in Hermes instead of migrating them
Set API keys fresh in Hermes instead of migrating them.
Expected: Done before you move to the next step.
Use hermes import-agent --sync --dry-run later to see what changed at
Use hermes import-agent --sync --dry-run later to see what changed at the source.
Expected: Done before you move to the next step.
Sample prompt from the pack
Apply this workflow to [your project]: 1. Install the plugin: hermes plugins install agent-importers. 2. Preview: hermes import-agent claude-code --dry-run (or codex, cursor, openclaw). 3. Read the per-item plan, especially MCP servers and command allow lists. 4. Apply without --overwrite so existing Hermes items are kept. 5. Set API keys fresh in Hermes instead of migrating them. 6. Use hermes import-agent --sync --dry-run later to see what changed at the source. Stop and ask me before anything irreversible: deploys, payments, sends or deletes.
Adapted by PaperChaseWebb. Not the original author's prompt.
Free preview of the file
# Move your Claude Code, Codex, Cursor or OpenClaw setup into Hermes with a dry run first PaperChase agent use case (free feed entry), version 1.0. Source: [Nous Research (Hermes Agent docs); workflow write-up by @Cuiszt_Cui](https://hermes-agent.nousresearch.com/docs/user-guide/import-from-other-agents), 2026-10-30. ## What they did Install the plugin, run hermes import-agent with the source agent and --dry-run, read the plan, then apply. Instruction files and memories become Hermes memory entries, Bash permission rules become allow and deny lists, MCP servers land in the config and skills are copied. Existing items that clash are reported and skipped unless you pass --overwrite, and --sync later pulls in changes from the source. A builder on X wrote it up as a five-step switch, and the Hermes docs confirm the commands. ## Worth knowing The dry run and the skip-on-conflict default are what make this safe to try. API keys are never copied for Claude Code, Codex or Cursor; for OpenClaw they only move with --migrate-secrets, so leave that off and set keys fresh. Review imported allow lists before trusting them, since a loose rule copies over as loose.
Worth knowing
- The dry run and the skip-on-conflict default are what make this safe to try. API keys are never copied for Claude Code, Codex or Cursor; for OpenClaw they only move with --migrate-secrets, so leave that off and set keys fresh. Review imported allow lists before trusting them, since a loose rule copies over as loose.
- Figures are as reported by the original author and were not re-measured by us.
Questions
Where does this come from?
A public post credited to Nous Research (Hermes Agent docs); workflow write-up by @Cuiszt_Cui. Source: https://hermes-agent.nousresearch.com/docs/user-guide/import-from-other-agents
Is it free?
Yes. Feed entries are free to read and download.
Details
Version 1.0 · Updated Oct 30, 2026 · Markdown version of this page
License: Personal and commercial use. Credit the original source when you share the workflow. Download terms
Related
AGENTS.md, CLAUDE.md and Cursor rules starter files
Six fill-in instruction files for coding agents (base, Next.js plus Supabase, FastAPI, browser game, CLAUDE.md pointer, scoped Cursor rules), an Approvals section that makes the agent stop and wait for your yes, a table of what Grok Bot, Claude Code, Codex, Hermes and Cursor each read, a read-only checker for your rule files and 9 prompts to write, trim and test your own.
Ask-first rules for AI agents: hard nos, approval cards and a test set
Paste-in rules that make an agent ask before it sends, spends, posts or deletes, define what a real yes is, and stop retries after a no, plus 12 test scenarios to check it.