Hermes Agent Cursor Import For Business: Should Your Team Move Its Cursor Setup Into Hermes?

Hermes Agent Cursor import lets a business move the instructions, tools and skills it built up in Cursor into Hermes without retyping a single rule.

For an owner, the real question is whether that saves enough rework to justify switching an agent over.

My answer is yes when the Cursor setup holds rules your team relies on, and here is how to judge it for your business.

Want a second pair of eyes on where agents fit in your marketing? Book a free call with my team.

The short answer for a business owner

Nous Research added Cursor to its importer in Hermes Agent v0.22.4, released on 21 October 2026.

The import is one command, it previews everything first, and it leaves passwords and API keys behind.

That makes it a low-risk trial: you can see exactly what would move before you commit.

The work it saves is the slow part of any switch, rewriting house rules and reconnecting tools.

If your Cursor folder is mostly empty, the import will be quick and the business case is weak.

If it holds months of rules, tools and skills, this is the cheapest way to give Hermes the same knowledge.

What actually moves from Cursor, in plain English

What your team built in Cursor	Where it ends up in Hermes
The main instructions file (AGENTS.md)	Hermes memory
House rules saved in the rules folder	Hermes memory, without Cursor's file-matching settings
Connected tools set up as MCP servers	The Hermes config file
Reusable skills	A Cursor imports folder in Hermes skills

The full mapping sits in the official import guide.

Anything your team wrote down once in Cursor, Hermes now reads too.

The import writes into Hermes; it reads from Cursor.

Your team's Cursor setup is the source, and Hermes becomes a second home for the same rules.

What stays behind on purpose

The importer never reads Cursor's credential file, ~/.cursor/cli-config.json.

Tool settings that look like secrets, such as tokens or API keys, are removed and listed in a report.

For a business, that is the right default.

Somebody on your side adds each key back on purpose, so nothing sensitive moves without a decision.

If someone runs the import from a script rather than by hand, it still stops at the preview unless they add --yes.

That protects you from a half-checked import going live by accident.

Use case 1: a local shop with a freelancer's Cursor rules

Picture a bakery that paid a freelancer to set up Cursor with rules for its website copy and product pages.

The freelancer has moved on, and the owner wants an agent that can also run scheduled jobs.

One import brings those rules into Hermes memory, so the new agent follows the same tone and product rules on day one.

Hermes can then run jobs on a timer through its built-in scheduler, such as a weekly check of the menu page.

The same pattern fits a trades business with a booking page, a salon with a services list, or a consultant with a template library.

If the rules exist in Cursor today, the import saves rewriting them.

The owner does not need to touch a terminal; the freelancer or any technical helper can run the three commands in a few minutes.

Use case 2: a service firm that wrote its house rules once

An accountancy practice spent an afternoon writing rules about client naming, file formats and what never goes in an email.

Rewriting that by hand for a second agent invites mistakes.

The import carries every rule body across and deduplicates against anything already in Hermes memory.

One partner reviews the preview, approves it, and the whole practice works from the same rules.

The practice also keeps a safety net.

Before any memory is merged, the importer saves the old MEMORY.md as a timestamped backup.

If the partner does not like the result, the previous version is one file away.

🔥 Want the agent setup small teams are copying right now? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members running agents in real businesses. → Join the AI Profit Boardroom

Use case 3: an agency running one Hermes profile per client

Agencies juggle clients with different rules, so mixing them in one agent is asking for trouble.

Hermes profiles solve that, and the importer writes into whichever profile you name with hermes -p <name>.

Point each import at a client's Cursor folder with --source, and each client gets its own clean profile.

New profiles cloned with --sync-imports keep pulling from the same source.

This also helps when a client relationship ends.

Their rules, tools and skills live in their own profile, so nothing leaks into the next client's work.

A broken settings file in one client's folder becomes a single error in the report while everything else still imports.

Running Cursor and Hermes side by side without double work

You do not have to retire Cursor to try Hermes.

Every import is registered, and hermes import-agent --sync pulls in only what changed since last time.

The docs say it is safe to run on a schedule, so a daily job keeps the two in step.

Your team keeps editing rules where they already work, and Hermes picks up the changes overnight.

What Hermes adds once your Cursor setup is inside

The point of moving is not to copy Cursor; it is to get jobs Hermes can do on its own.

The Hermes scheduler runs one-off or recurring tasks, can attach skills to a job, and delivers results back to a chat, local files or other configured targets.

Jobs can also fire from a webhook when something happens, instead of waiting for the next tick.

For a small business, that means the rules your team wrote in Cursor now guide work that happens while nobody is at a keyboard.

A weekly content check, a daily summary of new enquiries, a morning report on site changes: all of it reads the same imported rules.

Where the time saving comes from

I will not put a number on it, because every setup is different.

The saving comes from three jobs you no longer do by hand: copying rules, re-entering tool settings and rebuilding skills.

The preview also saves the meeting where everyone asks what moved, because the report answers it line by line.

The bigger your rules folder, the more you skip.

Ask the person who set up Cursor for an hour of their time on day one.

They know which rules matter, and the preview makes their review quick.

None of this replaces a person checking the work.

Scheduled jobs still need someone to read the results for the first few weeks, until you trust the rules they follow.

Which plan you need

The importer is the agent-importers plugin from Nous Research's official plugins repo, published under the MIT licence.

There is no separate plan or tier for it.

Install it once per profile with hermes plugins install agent-importers, or let hermes setup install it when it spots Cursor on the machine.

You will still need a model provider in Hermes, because keys never come across.

The plugin is maintained by Nous Research in its official plugins repo, alongside the other Hermes plugins.

Owners who already run Hermes for Claude Code or Codex imports get Cursor through the same plugin with no extra install.

The risks to manage before you switch anyone

• Rule scoping goes: Cursor's file-matching settings are stripped, so a rule meant for one file type now applies everywhere.
• Tools need keys again: any connected tool that used a token stops working until someone re-adds it.
• Skills can clash: two skills with the same name in different folders are reported as a conflict and skipped.
• Old installs ignore Cursor: a Hermes build with the importer still built in runs the old command, so update first.
• Existing Hermes skills win: same-name items are skipped unless you choose --overwrite.

None of these risks are hidden: every one of them shows up in the preview or the report.

The owner's job is to make sure somebody reads both.

Write those five risks on the rollout checklist and tick each one off as the report clears it.

📞 Need a plan for which business jobs to hand to an agent? Book a free SEO strategy session and we will walk through your site, your content and where Hermes earns its keep. → Get your free strategy session

A one-week rollout for a small team

1. Day 1: run hermes import-agent cursor --dry-run and read the plan with whoever owns the rules.
2. Day 2: run the real import and pick a model provider in hermes setup.
3. Day 3: re-add tool keys from the report, one tool at a time.
4. Day 4: add notes to rules that used to apply only to certain files.
5. Day 5: schedule the daily sync and give Hermes one real job.

After day five, check in once a week.

Ask whoever edits the Cursor rules whether the Hermes jobs are following them, and fix any rule that reads too broadly now its scoping is gone.

Most teams only need that check for the first few weeks.

How this differs from the Claude Code and Codex imports

I wrote up the wider tool, including Claude Code and Codex, in my Hermes import agent guide for teams.

Cursor is the one with a rules folder, which is why the scoping risk only shows up here.

It also brings no command approvals, so you set Hermes approvals yourself.

Both imports share the same rule on secrets, which is the part your accountant or IT person will ask about first.

Agencies get the most from the Cursor route, because one client per profile keeps rule folders separate from day one.

My decision for most small businesses

If your Cursor setup holds rules your team depends on, run the dry run this week.

It costs an afternoon, it shows you every item, and nothing is written until you say yes.

If you want to see how other owners run Hermes once it is set up, the AI Profit Boardroom has the walkthroughs.

Also On Our Network

• 🌐 The six-step run order for importing a Cursor setup into Hermes
• 🌐 A scorecard verdict on the Cursor import, rated 8.3 out of 10
• 🌐 Five copy-paste prompts that get your agent importing Cursor
• 🌐 Which AI models to run after a Cursor import, with live GoldieBench scores

FAQ: Hermes Agent Cursor Import For Business

Does my team have to stop using Cursor?

No. The import is registered for sync, so Cursor can stay where rules get edited and a daily hermes import-agent --sync pulls changes into Hermes.

Is there a paid plan for the Cursor importer?

No separate plan exists. It is the MIT-licensed agent-importers plugin from Nous Research, installed with hermes plugins install agent-importers.

Will our passwords and API keys move across?

No. Cursor's credential file is never read, and secret-looking tool settings are stripped and listed so someone re-adds them on purpose.

Can an agency keep each client separate?

Yes. Import each client's Cursor folder into its own Hermes profile with hermes -p <name> and --source.

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

About Julian

I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.

I help business owners scale with AI agents, automation and SEO.

• I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
• I've grown a YouTube channel to 400,000+ subscribers.
• I wrote "Link Building Mastery".
• My Udemy courses have taught over 29,000 students.

→ Get my best AI training inside the AI Profit Boardroom

Run the dry run with whoever owns your rules, and if you want help deciding what to automate, book a free SEO strategy session or join the AI Profit Boardroom before you roll out Hermes Agent Cursor.