Hermes Agent Cursor: Complete Guide (2026)

To move your Hermes Agent Cursor setup across, run hermes import-agent cursor: it copies your Cursor rules, AGENTS.md, MCP servers and skills from the ~/.cursor folder into Hermes, shows a preview first, and never copies your credentials. Cursor support arrived with the agent-importers plugin, listed as new in the Hermes v0.22.4 release notes on 21 October 2026.

📺 Watch: NEW Hermes Plugin Update is INSANELY GOOD!

🔥 Get the Agent OS as a free bonus: AI Profit Boardroom members get the full Agent OS zip, prompt libraries, daily tutorials and weekly live coaching calls. → Get inside

This page is Cursor-only. For the command in general, including Claude Code and Codex, see our Hermes import-agent guide. Coming from OpenClaw instead? Read how to migrate OpenClaw to Hermes.

Why import Cursor into Hermes at all

Cursor is where you edit code. Hermes is an agent that runs on its own: in chat apps, on a schedule, across profiles. Most people who use both end up writing the same rules twice and setting up the same MCP servers twice.

The importer fixes that. You keep writing rules in Cursor. Hermes picks them up. One source of truth, two tools.

The command used to live inside Hermes core. On 21 October 2026 it moved into the official agent-importers plugin, and Cursor joined Claude Code, Codex CLI and OpenClaw as a supported source in the same change. The flags and the sync file stayed the same, so older guides for the command still apply.

We share the exact rule files and agent setups that work for business tasks inside the AI Profit Boardroom, $69/mo, with coaching calls every week.

What the Hermes Agent Cursor import brings over

This mapping comes straight from the agent-importers README on GitHub.

In Cursor (~/.cursor)	Lands in Hermes as	Notes
AGENTS.md	Memory entries in memories/MEMORY.md	Merged and deduplicated with what you have
User Rules: rules folder, .md and .mdc files	Memory entries in memories/MEMORY.md	.mdc routing frontmatter is stripped; only the rule body comes over
mcp.json, mcpServers block	mcp_servers in config.yaml	Secret-looking env vars and headers are stripped and listed
Skills: any folder holding SKILL.md	skills/cursor-imports/ plus the skill name	Category folders are allowed
cli-config.json	Never read	Credentials stay in Cursor

Two details matter. First, the .mdc frontmatter fields (description, globs, alwaysApply) are Cursor routing metadata, so the importer drops them. Your rule text arrives, but the "only for these files" logic does not. Second, a skill is the folder holding SKILL.md. So a skill at skills/shipping/land-it imports as cursor-imports/land-it. Two skills with the same name in different folders are reported as a conflict.

📺 Watch: Hermes3D Is INSANE: AI Agents Now Have a 3D Office

What does not come across

API keys and tokens. MCP environment variables or headers with names like _TOKEN, _API_KEY or Authorization are stripped. The report lists each one so you can re-add it on purpose, through hermes setup or the profile's .env file.
Cursor's credential file. cli-config.json is never read.
Project rule targeting. Glob and alwaysApply settings are removed. In Hermes the rule becomes a memory entry.
Anything outside ~/.cursor. The default source is your home Cursor folder. Point it elsewhere with --source.

Step by step: import Cursor into Hermes

Install the plugin. Run hermes plugins install agent-importers. The plugin needs Hermes 0.21.6 or newer.
Preview. Run hermes import-agent cursor --dry-run. Nothing touches disk. You see every rule, server and skill it found.
Import. Run hermes import-agent cursor. It shows the preview again and asks before writing.
Handle conflicts. MCP servers and skills that already exist with the same name are skipped. Add --overwrite to replace them, and --yes to skip prompts.
Re-add secrets. Check the report for stripped keys and put them in the profile's .env.
Test. Start a chat and ask Hermes what rules it follows. Your Cursor rules should show up as memory.

Before it writes, the importer backs up your existing MEMORY.md with a timestamp. If your config.yaml cannot be read, it records an error and leaves the file untouched. Writes keep your comments.

Want to import into a different profile, such as a coding-only agent? Use hermes -p with the profile name before import-agent. Our guide to Hermes multiple profiles covers the setup.

📺 Watch: Hermes AI Agents Just Went Portable

The setup shortcut: Hermes asks for you

On a fresh install you may not need the command at all. Hermes's first-time hermes setup now has a "Coming from another agent?" step. It checks for a ~/.cursor folder, along with OpenClaw, Claude Code and Codex. When it finds one, it asks "Import your setup from Cursor?"

Say yes, and setup installs the agent-importers plugin from the catalog, then runs the same import with the same preview and confirmation. Say no, and it prints the commands to run later. This step was added to Hermes on 22 October 2026, per the commit history of the hermes-agent repo.

Not sure if moving your coding setup into an agent is worth it for your business? Book a free AI strategy session and we will look at it with you.

Keep Cursor and Hermes in sync

You do not have to pick one tool. Every successful import registers its source. Then hermes import-agent --sync re-imports any source whose files changed, with no prompts.

Runs well on a schedule. The README says it fits a cron job.
Only real changes trigger it. It compares a digest of exactly the files it reads. Credential files never trigger a sync.
Your edits are safe. If you changed an imported skill inside Hermes, sync treats it as a conflict and leaves it alone.
Failed runs retry. A run with errors keeps the old digest, so the next sync tries again.

New profile? hermes profile create with --clone --sync-imports carries the sync list over, so the new profile pulls from the same Cursor folder.

Common problems and fixes

"No supported agent setup found". Hermes did not find a ~/.cursor folder. If your Cursor files live somewhere else, pass the path with --source.
"Multiple agent setups detected". You ran the command without a name and Hermes found more than one agent. Name it: hermes import-agent cursor.
The import stops after the preview. Runs without a terminal, such as scripts, stop after the preview unless you pass --yes.
An MCP server imports but will not connect. Its key was probably stripped. Check the report and add the key to the profile's .env.
A skill was skipped. A skill with the same name already exists in Hermes, or two Cursor skills share a name. Rename one, or use --overwrite if you want the Cursor copy to win.
Setup says the import did not run. Your installed plugin may be older than its Cursor support. Run hermes plugins update agent-importers, then try again.

Each of these messages comes from the plugin's own code, so the fix is usually one flag away. Still stuck after that? Bring it to a free AI strategy session.

Using Hermes alongside Cursor

Once both share rules and MCP servers, split the work by where it runs best.

Cursor for hands-on editing inside your codebase.
Hermes for jobs that run without you: scheduled reports, chat-app replies, research. For web tasks that need a real browser, the Hermes Camofox plugin is worth a look.
Slash commands keep Hermes fast to steer. See our list of Hermes Agent slash commands.

For the bigger picture of how agents, tools and profiles fit together, read our Agent OS guide. To pick the model that drives Hermes, check the Goldie Bench.

FAQ

Does hermes import-agent copy my Cursor API keys?

No. Cursor's cli-config.json is never read, and secret-looking MCP env vars and headers are stripped and listed in the report.

Do Cursor project rules keep their file targeting?

No. The .mdc frontmatter, including globs and alwaysApply, is stripped. Only the rule body is imported, as a memory entry.

Can I import Cursor and Claude Code into the same profile?

Yes. Run hermes import-agent cursor and then hermes import-agent claude-code. With no name, the command only auto-detects when it finds a single setup; with several, it asks you to pick one. Memory entries are merged and deduplicated.