Compare

Bernstein vs Hermes Agent (Nous Research): quick decision guide

Hermes Agent (Nous Research) CLI adapter.

Page built on 2026-08-16 from data/adapters-meta.json. Every claim below links to its primary source.

Install both

Hermes Agent (Nous Research)

curl -fsSL

Bernstein

pipx install bernstein

Apache-2.0. Deterministic Python scheduler.

Feature matrix

Capability	Hermes Agent (Nous Research)	Bernstein
Install method	curl -fsSL	pipx install bernstein
License	Not recorded	Apache-2.0
Authentication	Not recorded	Per-agent credential scoping (no shared key)
Multi-agent orchestration	One agent in a terminal	Hermes Agent (Nous Research) plus 40+ other adapters in parallel worktrees
MCP support	Not measured	Yes
Parallel-safe in worktrees	Not measured	Yes (designed around git worktrees)
HMAC-chained audit log	No	Yes (RFC 2104 SHA-256 chain in .sdd/)
Deterministic scheduler	Not applicable (single-agent CLI)	Yes (Deterministic Python scheduler)

Adapter source: src/bernstein/adapters/hermes.py | Upstream homepage: hermes-agent.nousresearch.com

Verifiable facts

The brief for this surface requires at least three facts that a reader can verify against a primary source. The list below is built from the bernstein adapter source and, when available, the upstream project's own pages.

Bernstein ships a Hermes Agent (Nous Research) adapter at src/bernstein/adapters/hermes.py that wraps the upstream CLI as one of 42 routable agents. [source: bernstein adapter source, as of 2026-08-16]
Upstream install command, as recorded in the bernstein adapter, is "curl -fsSL". [source: upstream docs, as of 2026-08-16]
Bernstein is an open-source Multi-agent orchestrator licensed Apache-2.0, with a deterministic Python scheduler that routes work across CLI agents in parallel git worktrees. [source: bernstein repo, as of 2026-08-16]

Where Hermes Agent (Nous Research) fits in Bernstein

Bernstein registers Hermes Agent (Nous Research) under the slug "hermes" and the registry name "hermes". The adapter source lives at src/bernstein/adapters/hermes.py in the bernstein repo and was last touched at build time 2026-08-16. The Hermes Agent (Nous Research) adapter file is 184 lines and 7,174 bytes long, fingerprinted 5a8bd9a67067e299 (first 16 hex chars of SHA-256). Operators install Hermes Agent (Nous Research) on a worker box with "curl -fsSL" before Bernstein routes any task to it. No upstream GitHub repository is recorded in the bernstein adapter for Hermes Agent (Nous Research); refer to the upstream vendor's documentation when auditing. The Hermes Agent (Nous Research) project's homepage at hermes-agent.nousresearch.com is the primary source for upstream release notes. The bernstein adapter file for Hermes Agent (Nous Research) does not yet carry a "Last verified against upstream" line; this means the adapter still tracks an unpinned upstream binary. Bernstein routes tasks to Hermes Agent (Nous Research) when its pass rate on similar work clears the configured threshold, otherwise the deterministic Python scheduler picks a different adapter from the 40+ adapter catalog.

Adapter source excerpt

The module docstring of the Hermes Agent (Nous Research) adapter, as it stands in the bernstein repo. Punctuation is normalised for the web; the wording is the author's. Length: 41 characters.

Hermes Agent (Nous Research) CLI adapter.

Adapter telemetry

Registry name	`hermes`
Adapter class	`Hermes Agent (Nous Research)`
Source file	`src/bernstein/adapters/hermes.py`
Source file size	184 lines, 7,174 bytes
Source SHA-256	`5a8bd9a67067e29941a4b73439012eeb4302ca53ca70a24db15db50084f5870c`
Category bucket	cli-family
Upstream repo	Not derivable from adapter source
Upstream homepage	hermes-agent.nousresearch.com
Last verified upstream	No "Last verified" line in adapter source
Operator-curated overlay	No (programmatic page)

When to pick which

Choose Hermes Agent (Nous Research)

Reach for Hermes Agent (Nous Research) when the work is a single thread that fits one agent: in a single-process terminal session, designed for single-instance use per repo. Auth model is configured per upstream docs. You skip the orchestrator round-trip and get the smallest possible surface between you and the model.

Choose Bernstein

Wrap Hermes Agent (Nous Research) under Bernstein when the goal splits into parallel tasks, when you want an HMAC-chained audit log on every routing decision, or when a deterministic Python scheduler (no LLM picking who runs what) is a hard requirement.

FAQ

Does Bernstein replace Hermes Agent (Nous Research)?

No. Bernstein wraps Hermes Agent (Nous Research) as one of 40+ CLI adapters and routes tasks to it based on per-task pass-rate history. Hermes Agent (Nous Research) keeps running unchanged; Bernstein decides when it gets work.

Can I run Hermes Agent (Nous Research) alongside other agents in the same repo?

Yes. Each agent runs in its own git worktree under .sdd/worktrees/{session_id}, so file edits never collide. Bernstein merges results back to the trunk only after the configured quality gates (lint, types, tests) pass.

Is this comparison page handwritten?

No. The template is fixed; every fact and every link is pulled from the bernstein adapter source in the master branch and (when available) the upstream project's own pages. The data extractor lives at scripts/gen-compare-data.mjs. No LLM writes the prose.