HermesWatcher
Search⌘K For brandsSetup help
StartStart hereSetup plannerInstall Hermes AgentChat from your phoneYour first 24 hours
Use casesWorkflow blueprintsCase studiesUse-case collectionsCommunity libraryPrompt library
LearnWhat is Hermes Agent?Guideswitcheer's WingtipsTopicsFAQCommand cheat sheetGlossarySOUL.md gallery
ToolsTools & integrationsAll messaging platformsSkills directoryPlugins directorySkills, plugins & MCP
TroubleshootReleases
Work with usServicesNewsletterFor brands: partner with usFor AI agentsContactAboutFollow @HermesWatcher on X ↗ (opens in a new tab)

witcheer's Wingtips #36: hermes import-agent

Republished in his own words, with credit.

witcheerBy witcheer · Nous Research

Back to wingtips

#36 · hermes import-agent

· Setup & config · CLI

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!

SourcesHermes docs: Import From Other Agents

All tips are written by witcheer and collected here with credit. Card images stay on his X posts.

witcheer says each tip ran on a real Hermes box before it shipped. Hermes changes fast, so check your version and the linked doc.