Hermes LoopHermes Loop
Control room

Welcome back, Operator

7 missions on file · 9 items need attention

Start here

Pick a real Hermes-style capability to test

How it works
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.

Start here
Try a task. Each one runs a real Hermes-driven crew.
How it works →
Mental model
How Hermes Loop works
Full system map →
Concrete uses

What people can actually do with it

Queued
1
Running
0
Waiting approval
3
Completed
4
Pending approvals
4
Attention required
  • 1 queued · 0 running
    Open queue →
    Waiting for the worker process to pick up. Make sure `npm run worker` is running.
  • 4 approvals pending
    Review →
    Drafts, trade tickets, exports, gated tools.
  • 3 memory suggestions
    Open vault →
    Inferred preferences awaiting accept / reject.
  • 2 memory hygiene flags
    Run hygiene →
    Duplicates, conflicts, stale or low-confidence.
Hermes runtime · sandbox
Runtime tools

Governed terminal_exec + python_rpc for diagnostic crews. Risky commands wait for your approval; safe diagnostics run unapproved.

Hermes connected
Live at https://openrouter.ai/api/v1
Active operations
Inbox
Triage layer between raw requests and missions
Open inbox →
1
New
3
Triaged
0
Converted
  • [demo] Watch the AI semis space (NVDA, AVGO, AMD) and brief me every weekday mortriaged
  • [mobile] Set up a weekly Monday QA audit for my landing page.new
  • [mobile] Audit https://demo.acme-saas.test for conversion + a11y issues.triaged
  • [demo] Audit https://demo.acme-saas.test for conversion + accessibility issues.triaged
Job queue
Persistent, retryable background work
Open queue →
1
Queued
0
Running
0
Waiting
0
Failed
2 completed totalRun due →
Tool activity
All tool executions across your missions
11Completed
3Failed
0Blocked
Trust & proof
Workflow receipts
Hashed proof per mission · risk roll-up to the trust ledger
2
Low
2
Medium
0
High
Memory intelligence
Memory vault
Pinned + recently used memories injected into agent prompts
  • GLOBALpinnedused 2h ago
    [demo] Operator timezone: Europe/London (UK)
    Schedules and follow-ups should default to UK time unless the user specifies otherwise.
  • CREWpinnedused 2h ago
    [demo] Always state simulation only on paper trades
    Every paper-trade output must clearly state it is simulation only. No 'execute', 'fill', or live-trading language. Risk under 1.5% of book per trade.
  • CREWpinnedused 2h ago
    [demo] Prefer calm, firm tone for refund disputes
    When drafting refund or warranty disputes, default to a calm but firm voice with a 7-business-day window. Avoid ALL CAPS, exclamation marks, or threatening legal action.
  • CONTACTcreated 2h ago
    [demo] Vendor 'Acme' takes 5–7 business days to respond
    Recurring vendor 'Acme' has a typical 5–7 business day response window for refund tickets. Set follow-up at +5d, escalate at +10d.
  • CREWused 2h ago
    Approved paper-trade pattern
    Operator approved a simulated trade with explicit invalidation and stop. Keep this pattern: thesis → invalidation → stop → target → confidence.
  • CREWused 2h ago
    [demo] Bug Hunter — concise bullets in reports
    QA reports should be brief: bullets, not prose. One line per issue, severity prefix, link to step.

Missions

Most recent first
New mission →

Audit feed

Recent events
mission.completed2h ago
All approvals resolved.
debugger crew
approval.approved2h ago
Approve custom crew report → APPROVED
debugger crew
mission.learning_skipped2h ago
learning-error:Unexpected token '`', "```json [ "... is not valid JSON
debugger crew
mission.waiting_approval2h ago
Mission complete — items awaiting approval.
debugger crew
agent.completed2h ago
Report Agent completed
debugger crew
agent.started2h ago
Report Agent started
debugger crew
agent.completed2h ago
Fix Planner completed
debugger crew
agent.started2h ago
Fix Planner started
debugger crew
agent.completed2h ago
Error Analyst completed
debugger crew
tool.completed2h ago
terminal_exec completed
debugger crew
tool.started2h ago
terminal_exec started
debugger crew
agent.started2h ago
Error Analyst started
debugger crew
Scheduled work

Scheduled missions

Upcoming auto-runs from your active schedules
Manage schedules →

Deliverables

Latest outputs from completed missions