← All agent and harness briefs
Agent runtimeautonomousopscodingtestedunattended capable

Operational brief

Hermes Agent

Nous Research agent runtime with skills, memory, and multi-surface gateways.

Official Hermes Agent image from Nous Research

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.

How we classify it
Unattended scheduler/heartbeat with write-tools; failure has a real owner.
Runs unattended
Yes — that capability is documented in this brief.
Trigger
Human CLI/chat requests or configured schedules; cron execution needs the gateway scheduler running.
State
Profile-scoped memory files persist across sessions; job definitions and run outputs live on disk. Scheduled runs start fresh sessions rather than inheriting a chat implicitly.
Tools
Configured terminal and file tools can write within their granted host/backend authority. Cron toolsets are configurable, not automatically every available tool.
Human control
The operator owns schedules, toolsets and delivery targets, can interrupt interactive work, and can pause or remove jobs. This catalog retains the established desk-run owner scope, not a reliability guarantee for arbitrary tasks.

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.

Where it runs
Self-run CLI and gateway; terminal backend choice determines where commands execute.
Data boundary
Local memory and job/output files aren't a no-egress promise. Remote models, external tools and messaging delivery can receive selected context or results; retention depends on those services and your configuration.
Identity & permissions
The operator selects model/tool providers and messaging accounts. Profile-scoped memory helps separate agents; it isn't a blanket process or filesystem sandbox.
What it can write
host filesystem · shell · scheduled jobs
Surfaces
CLI · Telegram / Discord / Slack · Desktop · Cron / gateway
Export / lock-in
Memory files and plain-JSON jobs are inspectable local state; cron outputs are Markdown files. Backing up those files isn't a certified migration of every provider or channel setting.

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.

Evidence status
tested
Source set
6 primary sources
Evidence review
2026-10-17

Sources on file

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.

04 / Change log

Related coverage

The brief tells you what the product is. Payloads track the changes that may alter the decision.