Run all of this inside the full Agent OS — join the AI Profit Boardroom →

agentos.guide › blog

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

By Julian Goldie · 7 November 2026 · agentos.guide

Two glowing lanes on a dark aubergine background, one carrying code branches and pull request nodes, the other carrying chat bubbles and a clock, meeting at a gold control panel

Hermes vs Copilot inside your Agent OS is a lane decision: GitHub Copilot owns the code that lives in your GitHub repos, and Hermes Agent owns the chats, schedules and reminders that wrap around it.

You don't have to crown a winner.

You give each one a job and write the boundary down where both can read it.

This guide gives you a quick start, five prompts to paste into Hermes, and a weekly rhythm for a small design studio.

Want my team to draw the lanes with you? Get your Backlink Gameplan, or try Polar Rank free for 3 days.

The two lanes at a glance

LaneHermes AgentGitHub Copilot
OwnsMessages, schedules, memory, researchCompletions, pull requests, reviews, repo automations
LivesOn your machine or server, behind one gatewayIn your editor, your terminal and GitHub's cloud
Reaches you inTelegram, Slack, WhatsApp, Teams, email and moreVS Code, JetBrains, Xcode, github.com, GitHub Mobile, Slack, Teams
Runs on a timer withCron jobsAutomations
Reads house rules fromAGENTS.md and SOUL.mdcopilot-instructions.md and AGENTS.md

No official comparison exists, so this split is my reading of the Hermes docs and GitHub's Copilot docs.

Where each one sits in your Agent OS

Think of Copilot as the specialist you call into a repo.

It completes code in the editor, plans and edits from Copilot CLI, and, as the Copilot cloud agent (formerly the Copilot coding agent), turns an assigned issue into a pull request on GitHub.

Think of Hermes as the operator who never logs off.

Its gateway keeps every session in one place since v0.23.0, so the terminal, Desktop, editor and chat bots all share one history (release notes).

The Agent OS job is to route work to the right one and keep the outputs organised.

Quick start in five moves

  1. Install Copilot CLI with npm install -g @github/copilot (Node.js 22 or later) and run copilot in your repo.
  2. Install Hermes with the one-line script from the installation page (Windows users get a PowerShell version).
  3. Run hermes model to choose a provider, then hermes gateway setup to connect Telegram or Slack.
  4. Install GitHub CLI v2.80.0 or later so Hermes can read Copilot sessions with gh agent-task list (GitHub CLI docs).
  5. Start Hermes from the repo folder, so it picks up the AGENTS.md you'll write in Prompt 1.

Prompt 1: write the lane rules into AGENTS.md

Both tools read AGENTS.md, so this is where the boundary belongs.

Read this repo's layout and any existing AGENTS.md. Add a section called
"Lanes" with these rules:
- Code changes go to GitHub Copilot as an issue or a Copilot CLI session.
- Hermes never pushes commits or merges pull requests in this repo.
- Hermes may read issues, pull requests and gh agent-task output, and
report on them.
Keep the rest of the file as it is. Show me the diff before saving.

Hermes's /init command can also write a fresh AGENTS.md from a repo scan if you don't have one yet.

GitHub notes that not every Copilot feature reads agent instruction files, so copy the lane rules into .github/copilot-instructions.md too.

🔥 Get the Agent OS that keeps Hermes and Copilot in their lanes

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 setups.

→ Join the AI Profit Boardroom

Prompt 2: a morning Copilot digest to Telegram

Create a cron job called "Copilot digest" that runs at 08:00 on weekdays.
Each run: in ~/repos/studio-site run gh agent-task list, then gh pr list.
Summarise which Copilot sessions finished, which pull requests wait for
my review, and anything that has been open longer than three days.
Deliver it to this Telegram chat. Read only: do not comment, label or merge.

Hermes manages jobs through its own cron tool, so you can create, pause and edit them in plain English (cron docs).

Leave cron_mode: deny in your approvals config, so a scheduled run stops if it ever reaches a dangerous command.

Prompt 3: turn a client message into a Copilot-ready issue

Here is a client's message: [paste]. Rewrite it as a GitHub issue for
Copilot: a one-line title, the current behaviour, the expected behaviour,
the files likely involved, and the test that should pass.
Draft only: show me the issue text and do not create it.

Once you're happy, you create the issue and assign it to Copilot yourself.

After assignment, the cloud agent won't see new comments on that issue, so any changes go on the pull request it opens (GitHub guide).

Hermes approvals cover risky commands, not messages or GitHub posts, which is why "draft only" sits in the prompt.

Prompt 4: run Hermes on your Copilot subscription

Got a Copilot plan already? Nous Research's github-copilot labs plugin turns it into a provider for Hermes.

hermes plugins install github-copilot
hermes auth add copilot

Then paste this into Hermes:

Show me which provider and model you're using for chat, for cron jobs and
for delegation. Explain what would change if I pinned the "Copilot digest"
job to the copilot provider. Don't change any config yet.

The plugin offers copilot for the Copilot API and copilot-acp, which drives your installed Copilot CLI over ACP (providers page).

Nous built it but marks it unsupported, and it no longer reads logins saved by the gh CLI or Copilot CLI, so sign in through Hermes once (plugin README).

Prompt 5: a Friday client note from merged work

Every Friday at 16:00, list pull requests merged this week in
~/repos/studio-site with gh pr list --state merged. Turn them into a
plain-English note for the client: what changed, what they should check,
what's next. Save it to ~/notes/client-updates/ and send me the file
in Telegram. Draft only: never email the client.

That's the hand-off in one job: Copilot did the code, and Hermes explains it.

📞 Want a second pair of eyes on your lanes?

Get your Backlink Gameplan and my team will check which jobs belong to Copilot and which to Hermes, or try Polar Rank free for 3 days.

Backlink Gameplan or try Polar Rank free for 3 days

A weekly rhythm for a small design studio

A two-person studio maintains five client sites, each in its own private GitHub repo.

  1. Monday: client emails come in; the designer pastes each one into Prompt 3 and turns the drafts into issues.
  2. Monday afternoon: the developer assigns the small issues to Copilot and keeps the tricky ones for a Copilot CLI session in plan mode.
  3. Every weekday at 08:00: the Prompt 2 digest lands in Telegram with what finished overnight.
  4. During review: the developer switches on Agent Merge's Watch and fix, so Copilot handles failing workflows and merge conflicts (GitHub changelog).
  5. Friday at 16:00: Prompt 5 writes each client note, and the designer reads and sends them.

Nothing in that week needs the two tools to talk to each other directly.

The repo, AGENTS.md and the gh CLI are the shared ground.

A salon or a plumber with no repo would keep only the Hermes half of this rhythm: the digests, the drafts and the reminders.

Safety settings for both lanes

Set these before the first scheduled run, not after.

If a job feels risky, make it read only first, watch it for a week, and only then let it write.

Gotchas to check before day one

Coming from Claude Code instead? My Hermes vs Claude Code guide splits that pairing the same way.

Verdict: which lane gets which job

🔥 Run the full Agent OS with Hermes inside

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 swapping prompts like these.

→ Join the AI Profit Boardroom

FAQ

Can Hermes see what the Copilot cloud agent is doing?

Yes, if GitHub CLI v2.80.0 or later is installed. Hermes can run gh agent-task list and summarise the sessions on a schedule.

Where should the lane rules live?

In AGENTS.md, which both tools read, with a copy in .github/copilot-instructions.md for Copilot features that skip agent files.

Should Hermes create GitHub issues for me?

Have it draft them and create them yourself. Hermes approvals cover risky commands, not posts or messages.

Does the github-copilot plugin reuse my gh login?

No. The labs plugin no longer reads gh CLI or Copilot CLI logins, so run hermes auth add copilot once.

Final word on Hermes vs Copilot

Paste Prompt 1 today, schedule Prompt 2 tomorrow, and get your Backlink Gameplan if you want help running hermes vs copilot as two lanes, or try Polar Rank free for 3 days.

About Julian

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

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

My YouTube channel has 400,000+ subscribers, and I run Goldie Agency, a seven-figure SEO agency.

→ Get my best AI training inside the AI Profit Boardroom

Related guides on agentos.guide

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

→ Grok Bot AI Full Course (Step By Step)

→ The Ghost Team

→ Hermes Agent Browser: What It Is, The Quick-Start And Where It Fits In An Agent OS

Get the whole Agent OS

The installable system behind every guide on this site — dashboard, agents, memory and pipelines — updated as new tools land, with 3,400+ members and four coaching calls a week.

Join the AI Profit Boardroom →

📺 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