Full Byte Developer.
HERMESMOVE

Import Claude Code settings into Hermes

Preview imported instructions and tools, then review permission rules and credentials that do not transfer.

Published · 2 sources

Hermes can import Claude Code instructions, skills and MCP settings, per its import guide. Preview the plan before writing changes. [1]

Install the importer and preview changes

The current guide installs the official plugin, then runs a dry preview. [1]

bash
hermes plugins install agent-importers
hermes import-agent claude-code --dry-run

You should see a per-item plan. The guide says dry runs do not write to disk. [1]

Review permissions before importing

The importer maps Bash allow and deny rules, but reports non-Bash rules such as Read(...) as unmapped. It skips slash commands and strips credentials. Rebuild missing protections before giving Hermes access to the project. [1]

Hermes' security guide says its file tools deny reads of project .env, .env.local, .env.production and .envrc files, while allowing writes. That specific rule does not describe protection for every secret path. [2]

Apply the import

bash
hermes import-agent claude-code

Review the report for skipped items. The same guide supports codex and cursor as source names. [1]

Preview later updates

bash
hermes import-agent --sync --dry-run

After reviewing the changes, apply them with:

bash
hermes import-agent --sync

Imported setup changes can now be reviewed separately from the credentials you configure in Hermes. [1]

Keep this guide

By Full Byte Developer

Original posts: Instagram post, Facebook post, Threads post, TikTok photos

Filed under AI agents, Security

Sources

  1. Hermes import guidehermes-agent.nousresearch.com
  2. Hermes security guidehermes-agent.nousresearch.com

Next in this stack