Comparison · facts verified 2026-09-24
General assistant, or software delivery line. Hermes Agent is Nous Research’s open-source, always-on personal agent: it learns across conversations, runs scheduled work, and reaches you through messaging platforms. Orbi is a GitHub-native software-engineering agent: it takes an Issue through implementation, independent review, and merge. They overlap when a developer asks an assistant to work with GitHub, but they are built around different jobs.
THE COMPETITOR, FROM ITS OWN MATERIALS
Hermes Agent describes itself as “the self-improving AI agent built by Nous Research.” Its official repository presents persistent memory, cross-session search, skill creation and self-improvement, scheduled automations, multiple terminal backends, and a messaging gateway. The repository was created on 2025-07-22, is MIT-licensed, and identifies Nous Research as its author.
Sources: official repository (description, creation date, MIT license); official Hermes site (product positioning) — verified 2026-09-24.
RELATED, NOT THE SAME CATEGORY
Hermes Agent and OpenClaw are separate open-source, self-hosted general assistants with overlapping messaging, memory, automation, and GitHub-tool surfaces. The official materials reviewed here do not present Hermes as an OpenClaw fork or as an affiliated project. Neither should be described as Orbi’s Issue-to-reviewed-merge delivery loop: that is Orbi’s distinct product boundary.
Sources: Hermes Agent official repository and OpenClaw official site (positioning and project identity); Orbi documentation (delivery loop) — verified 2026-09-24.
DEPLOYMENT AND CAPABILITY BOUNDARY
Hermes can run as a gateway on a machine you operate and be reached from Telegram, Discord, Slack, WhatsApp, Signal, or email. Its README explicitly gives a $5 VPS, a GPU cluster, and serverless backends as deployment examples. It supports provider choice through configuration and includes scheduled cron jobs, memory, skills, and terminal backends.
| Question | What the official materials establish | What they do not establish |
|---|---|---|
| GitHub | A bundled GitHub skill documents repository inspection, issues, pull requests, code review, and issue-to-PR workflows. | A documented, unattended GitHub Issue queue that autonomously claims, implements, tests, reviews, and merges work as one product loop. |
| Self-hosting | CLI and gateway can run on an operator’s machine, including a VPS; terminal backends include local, Docker, SSH, and others. | A hosted Hermes service is not required by the open-source repository; operating the server and credentials remains the operator’s job. |
| Always-on work | Gateway conversations and cron automations can run unattended and deliver to messaging platforms. | Always-on personal automation is not the same as Orbi’s GitHub-native delivery state machine. |
Sources: Hermes README; bundled GitHub skill documentation; cron documentation — verified 2026-09-24.
DIFFERENCES THAT DECIDE THE CHOICE
Hermes is a broad assistant that can use GitHub as one tool. Orbi is a software-engineering delivery system whose queue, state, evidence, and output are GitHub objects. Neither framing makes the other product lesser; it identifies the workflow each one optimizes.
| Dimension | Orbi | Hermes Agent |
|---|---|---|
| Positioning | Software-engineering agent and delivery system | General-purpose, always-on personal assistant |
| Task entry | GitHub Issue + ai-ready label | Conversation through gateway/CLI, or scheduled automation |
| GitHub outcome | Implementation → independent review/repair → ordinary PR → merge | GitHub skills can inspect and operate repositories; an Issue→PR run requires user-directed workflow and configuration |
| State | GitHub Issues, labels, branches, PRs, and run evidence | Persistent memory, sessions, skills, and agent configuration |
| Models | BYOK, OpenAI-compatible endpoints | Multiple providers and own endpoints; can switch with hermes model |
| Runs where | Operator’s machine and Git worktree | Operator’s machine/VPS, with local, container, SSH, and cloud backends |
| License | AGPL-3.0 or Sustainable Use License | MIT |
Sources: Orbi documentation and Orbi repository; Hermes repository and Hermes skills documentation — verified 2026-09-24.
AN HONEST READ
The practical boundary is not “can either model touch code?” Both can. It is whether GitHub delivery is the product’s primary state machine or one capability inside a personal assistant.
PROVENANCE
The facts on this page are a snapshot. All sources below were checked on 2026-09-24; re-check them before making an architectural decision.
PICK BY THE BOUNDARY
Hermes and Orbi overlap at the tools layer, including GitHub. Hermes is the broader always-on assistant; Orbi is the narrower system for moving repository work from Issue to reviewed merge.
One email a week about one real delivery. Unsubscribe anytime.
