agentos.guide › blog
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.
| Lane | Hermes Agent | GitHub Copilot |
|---|---|---|
| Owns | Messages, schedules, memory, research | Completions, pull requests, reviews, repo automations |
| Lives | On your machine or server, behind one gateway | In your editor, your terminal and GitHub's cloud |
| Reaches you in | Telegram, Slack, WhatsApp, Teams, email and more | VS Code, JetBrains, Xcode, github.com, GitHub Mobile, Slack, Teams |
| Runs on a timer with | Cron jobs | Automations |
| Reads house rules from | AGENTS.md and SOUL.md | copilot-instructions.md and AGENTS.md |
No official comparison exists, so this split is my reading of the Hermes docs and GitHub's Copilot docs.
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.
npm install -g @github/copilot (Node.js 22 or later) and run copilot in your repo.hermes model to choose a provider, then hermes gateway setup to connect Telegram or Slack.gh agent-task list (GitHub CLI docs).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.
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.
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.
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).
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.
A two-person studio maintains five client sites, each in its own private GitHub repo.
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.
Set these before the first scheduled run, not after.
~/.hermes/config.yaml, set approvals.mode to smart or manual and keep unattended_mode: deny for webhook and API sessions (security docs).--allow-all-tools, which gives Copilot the same file and shell access you have without asking; turn on /sandbox enable for anything you're unsure of.If a job feels risky, make it read only first, watch it for a week, and only then let it write.
hermes acp leaves out cron and messaging, so keep the schedules on the gateway.Coming from Claude Code instead? My Hermes vs Claude Code guide splits that pairing the same way.
🔥 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.
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.
In AGENTS.md, which both tools read, with a copy in .github/copilot-instructions.md for Copilot features that skip agent files.
Have it draft them and create them yourself. Hermes approvals cover risky commands, not posts or messages.
No. The labs plugin no longer reads gh CLI or Copilot CLI logins, so run hermes auth add copilot once.
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.
→ 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)
→ Hermes Agent Browser: What It Is, The Quick-Start And Where It Fits In An 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 👉