Operational brief
Hermes Agent
Nous Research agent runtime with skills, memory, and multi-surface gateways.

Choose it when
You want reusable skills and memory across chat surfaces, plus scheduled work whose tools, outputs and failures you own.
Skip it when
You want only an IDE coding assistant, or can't assign an owner to unattended jobs and their failures.
01 / Classification
Autonomy evidence
This is our classification, not a vendor badge. The record says what the product normally does. The gaps stay visible.
02 / Operations
Control reality
Useful agents eventually touch something real. This is the operational picture we have, not a promise hidden in a sales page.
03 / Receipts
Evidence ledger
Here is what this brief is built on. “Documented” means we found a source. “Tested” means this desk actually ran it. Those are different things.
Sources on file
- https://github.com/NousResearch/hermes-agent
- https://hermes-agent.nousresearch.com/docs
- https://raw.githubusercontent.com/NousResearch/hermes-agent/63d0b94120027d487c9a5235b9ec64b696af1b26/README.md
- https://api.github.com/repos/NousResearch/hermes-agent/releases/latest
- https://hermes-agent.nousresearch.com/docs/user-guide/features/cron
- https://hermes-agent.nousresearch.com/docs/user-guide/features/memory
- https://github.com/NousResearch/hermes-agent/blob/main/SECURITY.md
- Homepage · https://github.com/NousResearch/hermes-agent
Corrections
- 2026-10-13 · Removed the dated provider/auth snapshot from watch_for. Provider availability is deployment-specific, not a durable product capability claim.
- 2026-10-13 · Replaced a desk-payload date used as release metadata with upstream v0.21.7's API publication timestamp. Existing tested status remains limited to established desk-run operations, not that upstream release or all current docs.
- 2026-10-17 · Refreshed upstream release metadata from v0.21.7 to v0.22.2 using the release API publication timestamp. The release corrects v0.22.1's wrong-commit build, retains a known session-deletion issue for sessions run under the 0.22.1 gateway, and separates main-only v0.23.0 work. This is not an installed upgrade or an expansion of the established desk-run tested scope; the upstream release is not runtime-tested here.
Technical dossier
Technical review
Pillar weights describe the proposed rubric, not measured results. No overall score or security certification has been assigned.
Documentary claim ledger
Retained source snapshots; capture date and revision not recorded here. Source links point to mutable upstream documents. Quoted documentation is not a semantic audit or proof of installed behavior.
- https://github.com/NousResearch/hermes-agent/blob/main/SECURITY.md · summaries.architecture
- **Agent process.** The Python interpreter running Hermes Agent, including any Python modules it has loaded (skills, plugins, hook handlers). - **Terminal backend.** A pluggable execution target for the `terminal()` tool. The default runs commands directly on the host.
Documented architecture; choosing a boundary is editorial guidance, not a tested configuration.
- https://github.com/NousResearch/hermes-agent/blob/main/SECURITY.md · summaries.architecture
What this confines: anything the agent does by issuing shell or file operations. What this does **not** confine: everything the agent does in its own Python process.
Terminal-backend isolation isn't whole-process containment; installed behavior remains unverified.
- https://github.com/NousResearch/hermes-agent/blob/main/SECURITY.md · summaries.security
The default runs commands directly on the host.
Current upstream default, not an observation of this desk's active backend or installed version.
- https://github.com/NousResearch/hermes-agent/blob/main/SECURITY.md · summaries.security
That includes the code-execution tool (spawned as a host subprocess), MCP subprocesses (spawned from the agent's environment), plugin loading, hook dispatch, and skill loading (all imported into the agent interpreter).
Documented paths outside terminal-backend isolation, not a demonstrated escape or vulnerability finding.
- https://github.com/NousResearch/hermes-agent/blob/main/SECURITY.md · summaries.security
Whole-process wrapping runs the entire agent process tree inside a sandbox. Every code path — shell, code-execution, MCP, file tools, plugins, hooks, skill loading — is subject to the same filesystem, network, process, and (where applicable) inference policy.
Upstream posture description, not verified enforcement or an implementation guarantee from this desk.
- https://github.com/NousResearch/hermes-agent/blob/main/SECURITY.md · summaries.security
This is the supported posture when the agent ingests content from surfaces the operator does not control — the open web, inbound email, multi-user channels, untrusted MCP servers — and for production or shared deployments.
Upstream recommends whole-process wrapping for this threat model; no configuration change or lab test performed.
- https://github.com/NousResearch/hermes-agent · summaries.interoperability
Use any model you want — [Nous Portal](https://portal.nousresearch.com), OpenRouter, OpenAI, your own endpoint, and [many others](https://hermes-agent.nousresearch.com/docs/integrations/providers).
Documents provider/endpoint choices, not verified universal compatibility, availability or provider terms.
- https://github.com/NousResearch/hermes-agent · summaries.interoperability
Hermes has two entry points: start the terminal UI with `hermes`, or run the gateway and talk to it from Telegram, Discord, Slack, WhatsApp, Signal, or Email.
Documents messaging gateways, not delivery reliability or functioning account integrations at this desk.
- https://github.com/NousResearch/hermes-agent · summaries.interoperability
[MCP Integration](https://hermes-agent.nousresearch.com/docs/user-guide/features/mcp) | Connect any MCP server for extended capabilities
README documents MCP integration; linked guide wasn't fetched, and the vendor's broad wording isn't a tested compatibility guarantee.
- https://github.com/NousResearch/hermes-agent · summaries.developer_experience
Full TUI with multiline editing, slash-command autocomplete, conversation history, interrupt-and-redirect, and streaming tool output.
Documented interface affordances, not a usability study, installation test or developer-experience score.
- https://github.com/NousResearch/hermes-agent/blob/main/SECURITY.md · lab_evidence.limitations
Nothing inside the agent process constitutes containment — not the approval gate, not output redaction, not any pattern scanner, not any tool allowlist.
Documented trust model; neither an audit nor a prompt-injection result, and not evidence that all configurations are safe.
04 / Change log
Related coverage
The brief tells you what the product is. Payloads track the changes that may alter the decision.