# witcheer's Wingtips #36: hermes import-agent

Written by [witcheer](https://x.com/witcheer) at Nous Research. Republished with credit.

Canonical: https://hermeswatcher.com/wingtips/36  
Published: 2026-08-01  
[Original](https://notwitcheer.github.io/hermes-recipes/wingtips/36-hermes-import-agent/) · [On X](https://x.com/witcheer/status/2083360088593776765) · [Full collection](https://notwitcheer.github.io/hermes-recipes/) · [Official docs](https://hermes-agent.nousresearch.com/docs/user-guide/import-from-other-agents)

[Source Markdown](https://raw.githubusercontent.com/notwitcheer/hermes-recipes/8653fb699a137a32e81936fa33cabacd3f4f2095/docs/wingtips/36-hermes-import-agent.md): use this file as the base for relative links in the verbatim text below.

Sources: [Hermes docs: Import From Other Agents](https://hermes-agent.nousresearch.com/docs/user-guide/import-from-other-agents)


Hermes Wingtips #36: hermes import-agent

if you already run Claude Code or Codex CLI, your setup can move over to Hermes Agent in one command:

`hermes import-agent`

it auto-detects `~/.claude` or `~/.codex` and maps everything to its Hermes equivalent: 

global instructions become memories, skills come across as skills, MCP servers goes in your config, and Claude's permission rules become the command allowlist. API keys and credentials are never touched.

it always shows you the full plan before writing anything, and `--dry-run` previews without touching disk at all.

there is no need rebuilding the setup you already tuned!