agentos.guide › blog

Hermes vs Cursor: How To Run Both As Two Lanes In Your Agent OS, With 5 Copy-Paste Prompts

By Julian Goldie · 4 November 2026 · agentos.guide

Hermes vs Cursor inside your Agent OS is a question of lanes: Cursor edits the code in your repos, and Hermes Agent runs the always-on work that reaches people through chat, cron and memory.

You don't pick one.

You give each a job and let your Agent OS keep them apart.

This guide gives you a quick start, five prompts to paste into Hermes, and a weekly workflow for a small consultancy.

If you want my team to look at your lanes with you, book a free SEO strategy session.

The two lanes in one table

Neither vendor compares the two, so this split is based on how each set of docs describes its own tool: the Hermes docs and the Cursor docs.

What each tool is for, in one breath each

Cursor is an AI code editor: its Agent searches your repo, edits files, runs terminal commands and saves checkpoints you can restore if a change goes wrong.

Its cloud agents do the same work in isolated virtual machines and push their changes to a branch for you to review.

Hermes is an open-source agent from Nous Research that lives on a machine you choose and talks to you through more than twenty chat platforms.

It remembers you between sessions, runs jobs on a timer, and writes new skills when it works out how to do something.

That's why the boundary is easy to draw: one works on files, the other works on the week.

Quick start in four moves

1. Install Hermes with curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash, or the Desktop installer on Windows and macOS.
2. Run hermes model and connect a provider, such as Nous Portal, OpenRouter or Anthropic.
3. Install Cursor from its quickstart page and open your repo.
4. Start Hermes from the repo folder so it picks up the same rules Cursor uses.

That last move matters.

The Hermes tips page says it loads .cursorrules and .cursor/rules/*.mdc from the working directory without any copying.

Prompt 1: map which jobs go to which lane

Give Hermes your task list and let it sort the work before you build anything.

Here is my weekly task list. Sort every task into two lanes.
Lane A (Cursor): anything that ends in a code change, a pull request or a code review.
Lane B (Hermes): anything that ends in a message, a report, a reminder or a file.
For each Lane B task, suggest a cron schedule and a delivery channel.
Flag any task that would need both lanes and say which lane starts it.
Don't create any jobs yet. Show me the table first.

Ask for a table so you can check the split at a glance.

Expect a few tasks in both lanes, such as "fix the contact form and tell the client", and let Cursor start those while Hermes sends the follow-up.

Prompt 2: check which rule files Hermes is reading

Before the two tools share a repo, confirm they follow the same conventions.

From this working directory, list every context file you loaded:
AGENTS.md, .hermes.md, CLAUDE.md, .cursorrules and any .cursor/rules/*.mdc.
Summarise the rules from each file in one line.
Point out any rule in .cursor/rules that conflicts with AGENTS.md.
Suggest which rules should move to AGENTS.md so both agents follow them.

Cursor's rules docs ignore a plain .md file inside .cursor/rules, so ask Hermes to flag any of those too.

🔥 Get the Agent OS that runs Hermes in its own lane

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 sharing their Hermes and Cursor setups.

→ Join the AI Profit Boardroom

Prompt 3: bring your Cursor setup across with a dry run

If Cursor already holds your rules, MCP servers and skills, import them instead of rewriting them.

Install the agent-importers plugin if it isn't installed:
hermes plugins install agent-importers
Then run: hermes import-agent cursor --dry-run
Show me the plan item by item: memory entries, MCP servers, skills.
List every MCP header or env var that will be stripped as a secret.
Wait for my yes before running the real import.

The import guide says --dry-run never touches disk and credentials never come across.

For the full import walkthrough with every flag and the daily sync, use the Hermes Agent Cursor guide.

Prompt 4: schedule the client report Cursor can't send

This is the job Hermes owns outright.

Create a cron job called "Weekly client update".
Schedule: every Friday at 15:00 in my time zone.
Task: read this week's notes in ~/clients/notes, then draft one
short update per client with what shipped, what's next and any blockers.
Deliver to Slack so my account manager can edit before sending.
Start the job paused and show me the job id.

The cron docs list Slack, Telegram, email, local files and "all" as delivery targets.

Cron runs can't create more cron jobs, so a scheduled run can't spiral into new schedules.

Prompt 5: put Hermes in a second editor over ACP

Some teams want Hermes in an editor for the odd code task while Cursor stays the main one.

Set up ACP mode for me.
Install the ACP extra from my Hermes checkout, then run hermes acp --check.
Then give me the exact settings to add Hermes as an agent in Zed.
Tell me which tools I lose in ACP mode compared with the gateway.

The ACP page documents VS Code, Zed and JetBrains.

It does not document Cursor, so keep ACP for those editors.

In ACP mode Hermes drops messaging delivery and cron management, which is why the gateway stays the home for Prompt 4.

A weekly workflow for a small consultancy

Take a four-person marketing consultancy that also maintains landing pages for its clients.

1. Monday: Hermes sends each consultant a Telegram brief with the week's client calls from its memory and notes.
2. Tuesday to Thursday: the developer asks Cursor's Agent for landing page changes, approves the plan in Plan Mode and reviews each diff.
3. On every pull request: Bugbot reviews the change and leaves comments before merge.
4. Friday 15:00: the Prompt 4 cron job drafts every client update and drops them into Slack.
5. Friday 16:00: the account manager edits, sends and tells Hermes what to remember for next week.

Cursor never sends a client email.

Hermes never merges a pull request.

Where Cursor Automations still fit

Cursor Automations start cloud agents on a timer or when a pull request opens, CI finishes, a Slack message arrives or a webhook fires.

Use them when the timed job needs a repo: a nightly dependency check, a daily codebase digest, a bug triage from Slack.

Use Hermes cron when the timed job needs a person.

If you're unsure, ask where the result should land: a branch means Cursor, and an inbox or a chat means Hermes.

That one question settles most scheduling arguments before they start.

📞 Want a second pair of eyes on your two-lane setup?

Book a free SEO strategy session and my team will check which jobs belong in Cursor and which in Hermes.

→ Book your free strategy session

Three mistakes to avoid when running both

• Two agents on one repo at once. Let Cursor own branches and pull requests, and keep Hermes to reading the repo unless you ask it for a change.
• Rules in two places. Keep coding rules in .cursor/rules or AGENTS.md so both tools read the same file, rather than writing a second copy for Hermes.
• Reports from the wrong scheduler. A Cursor Automation can post to Slack, but a report for a client or a manager belongs in Hermes cron, where delivery options reach email and chat apps.

Safety settings to set once

• Leave Hermes on approvals.mode: smart, its default, and keep cron_mode: deny so scheduled runs can't execute dangerous commands, per the security page.
• Add your own always-blocked patterns under approvals.deny.
• In Cursor, use Auto-review in Settings > Agents > Approvals & Execution, and remember Cursor calls it no security boundary.
• Keep MCP keys out of shared files; the Hermes importer strips secret-looking values for a reason.

Your Hermes vs Cursor next step

Paste Prompt 1 today and get your task split on one page.

Paste Prompt 4 tomorrow and let the Friday report run itself.

Members of the AI Profit Boardroom get the Agent OS with these lanes already laid out.

If you'd like help, book a free strategy session with my team.

FAQ

Will Hermes follow my Cursor project rules?

Yes. Hermes loads .cursorrules and .cursor/rules/*.mdc from the working directory, so start it from the repo folder.

Can Hermes run inside Cursor through ACP?

The Hermes ACP docs cover VS Code, Zed and JetBrains, not Cursor, and Cursor's docs don't mention Hermes. Use a documented editor.

Should I schedule reports with Hermes cron or Cursor Automations?

Hermes cron for anything that ends with a person reading it, because it delivers to Slack, Telegram or email. Cursor Automations for timed jobs that need a repo.

Does the Cursor import copy my API keys?

No. hermes import-agent never reads Cursor's credential file and strips secret-looking MCP values, which it lists so you can add them back.

Final word on Hermes vs Cursor

Paste Prompt 1, schedule Prompt 4, and book a free strategy session if you want help running hermes vs cursor as two lanes.

Related guides on agentos.guide

→ Hermes Agent Cursor: Import Your Cursor Rules, MCP Servers And Skills Into Your Agent OS With Five Prompts

→ Hermes Import Agent: The Quick Start For Moving Claude Code And Codex Into Hermes, And How It Fits Your Agent OS

→ Hermes Agent For Business: 5 Jobs To Run In Your Agent OS

→ Hermes Delegation: Run Parallel Subagents In Your Agent OS With 5 Copy-Paste Prompts

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

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

← all guides on agentos.guide