Hermes LoopHermes Loop
How it works

Plain English: what Hermes Loop actually does.Hermes does the reasoning. Hermes Loop runs and proves the work.

Hermes Loop is the operator surface for the Hermes Agent. You describe a job, the system runs a crew of Hermes-driven subagents, gives them governed tools (browser, search, terminal, Python, vision, image, audio, memory), gates risky outputs behind your approval, and produces a hashed receipt that proves what happened.

Plain English

The control room for the Hermes Agent.

Hermes Agent is Nous Research's open-source autonomous agent — it lives on your server, remembers what it learns, and gets more capable the longer it runs. Hermes Loop is the operator surface: you launch missions, run named crews of subagents, gate risky outputs with approvals, and produce a hashed receipt that proves what happened.

What Hermes Agent gives you

The autonomous engine: persistent memory, subagents with their own conversations and terminals, natural-language cron, and native tools (web search, browser automation, vision, multi-model reasoning).

What Hermes Loop adds on top

The governance layer: crews, a job queue, approvals, hashed receipts, a trust ledger, evals, schema self-correction, real-cost accounting, and a full audit trail.

Why it is different

A chatbot gives an answer. The Hermes Agent does the work autonomously; Hermes Loop proves it: who ran, which tools were called, which memory was used, what was approved, and what hash signed off the run.

What to try first

Run Bug Hunter on /demo-target, approve the QA report, generate the receipt, then open Trust to see the run roll up into risk and proof.

The pieces

How this app relates to Hermes Agent

Hermes Agent is the engine. Hermes Loop is the control room.

Every Hermes Agent capability has a corresponding surface in this app that governs, audits, and proves it. Hermes Agent gives you autonomy; Hermes Loop gives you governance and proof.

Hermes Agent (the engine)
Hermes Loop (this app)
Isolated subagents with their own conversations + terminals
Native tools (web search, browser automation, vision, TTS, multi-model reasoning)
Multi-platform interface (Telegram, Discord, Slack, WhatsApp, Signal, Email, CLI)
Execution backends (local, Docker, SSH, Singularity, Modal)

What's wired right now

Every row below reads from the actual env. Statuses are live — if a provider isn't set up, the row tells you which env var to add. Hermes Loop never claims a feature is wired when it isn't.

Hermes (text)
READY
Configured. Default model: nousresearch/hermes-4-70b.
Multi-model routing
READY
Active. 1/4 roles explicitly routed (vision). Unset roles fall back to nousresearch/hermes-4-70b.
Web search
READY
Active provider: tavily.
Vision (multimodal)
READY
Configured.
Image generation
READY
Primary: Hermes (chat-completions + image modalities). Fal / Replicate are fallbacks.
Text-to-speech
READY
Primary: ElevenLabs. Voice ID: 21m00Tcm4TlvDq8ikWAM (default). eleven_multilingual_v2 model.
Integrations webhook
READY
Live. /api/integrations/webhook accepts posts. Set INTEGRATIONS_WEBHOOK_SECRET in production to require HMAC signing.
Runtime backend
READY
Active: local Node process. terminal_exec + python_rpc run on host. Set RUNTIME_BACKEND=docker (with Docker installed) to enable container isolation.
Discord
READY
Inbound: live (set DISCORD_WEBHOOK_SECRET to require signing). Outbound: optional (add DISCORD_WEBHOOK_URL or BOT_TOKEN for approval notifications).
Slack
READY
Live. Inbound route accepts posts. Set SLACK_SIGNING_SECRET in production to require Slack v0 signing.
Email inbound
READY
Live. Accepts SendGrid / Mailgun / Postmark / generic JSON. Set EMAIL_WEBHOOK_SECRET when fronted by a signing forwarder.
MCP (Model Context Protocol)
NEEDS PROVIDER
Set MCP_SERVERS to a JSON array of { name, url, headers? } to expose remote MCP tools to agents.
Cross-session memory recall
READY
Live. Every mission queries operator-approved memory across all prior sessions; the top matches are injected into the Triage Agent + first-step prompts.
Learning loop · autonomous skill creation
READY
Live. After a mission settles, Hermes Loop distils up to 3 durable lessons into Skill rows on the same crew. Future runs of that crew inject the top skills into their system prompt.

What you can click to test it

What Hermes Loop adds on top of Hermes

  • Approvals. Risky outputs (drafts, trades, exports, gated tool calls) wait for you. /approvals
  • Workflow receipts. Every mission ends with a hashed timeline and real cost. /receipts
  • Trust ledger. Aggregate reliability across runs. /trust
  • Memory governance. Operator-approved context with usage records and diffs. /memory
  • Evals harness. Real-Hermes test suite — exit code = failed cases.
  • Real-cost accounting. Real per-model rates fetched live, recorded on every receipt.
  • Learning loop. After every mission settles, Hermes Loop distils up to 3 reusable lessons into /skills. Future runs of the same crew inject them into their system prompt.
  • Cross-session memory recall. Every mission queries operator-approved memory across all prior sessions; the top matches are injected into the Triage Agent and first-step prompts.
  • MCP integration. Native MCP client. Set MCP_SERVERS and remote tools show up in the registry alongside built-ins.