Hermes

Hermes profiles that learn from every conversation.

--harness hermes

What you get

Hermes runs each agent in its own profile — a clean slate every time. With self-driving agents installed, the profile builds up across sessions: the agent learns from every chat, maintains its own knowledge pages, and walks into the next session already informed.

Learns from every conversation — preferences, decisions, and recurring patterns are captured automatically. The agent walks into the next session already knowing them.
Builds its own playbooks — the agent maintains long-form pages (a personal wiki) that self-rewrite from what it has learned.
One profile, one agent, one bank — clean isolation. Multiple agents on one machine never share memory.

Setup

1
Have hermes on PATH
The CLI shells out to hermes profile create, profile show, and reads the profile config. Install hermes-agent first if you haven't already.
```
curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash
```
2
Install the agent
One CLI call creates the Hermes profile, drops in the plugin, configures the connection, ingests seed content, and installs the agent-knowledge skill.
```
npx @vectorize-io/self-driving-agents install marketing/seo --harness hermes
```
3
Chat
Memory retains in the background as you talk.
```
hermes -p marketing-seo chat
```

How it works

The CLI runs hermes profile create <agent> --clone (or reuses the existing profile), copies the hindsight-sda plugin into <profile>/plugins/hindsight-sda/, writes <profile>/hindsight/config.json (api url, token, bank id), and edits <profile>/config.yaml to set memory.provider: hindsight and add hindsight-sda to plugins.enabled. The bundled Hindsight memory provider then auto-retains during chat. The agent-knowledge skill is dropped into <profile>/skills/agent-knowledge/SKILL.md and exposes the tools below.

Tools the agent gets

list_pagesList page ids and names.

get_pageRead the content of a page.

create_pageDeclare a new page recipe.

update_pageChange a page's name or source query.

delete_pageRemove a page.

recallSearch retained memories.

ingestAdd new text content as a memory.

Bank mapping

Each Hermes profile maps 1:1 to one bank. Bank id equals the agent name (and the profile name). Connection lives in <profile>/hindsight/config.json.

The CLI writes <profile>/hindsight/config.json with mode, api_url, api_key, bank_id, recall_budget, and memory_mode. Both the bundled memory provider and the hindsight-sda tool plugin read this same file — single source of truth.
bank_id is set to the agent name and bank_id_template is left empty, so every chat in the profile lands in the same bank.
On install the CLI looks for an existing connection in this order: <profile>/../hindsight/config.json, then OpenClaw's plugin config, then prompts. Re-running install with the same agent name reuses the profile and updates the config in place.
To re-map: edit <profile>/hindsight/config.json directly. No daemon restart needed — hermes reads it at the next chat.

Resources

hermes-agent on GitHub →Hermes docs →