Configure Hermes access to small LLM

This commit is contained in:
Frank committed 2026-08-25 17:55:52 -07:00
1 parent 96f5ae6fe1
commit e1f05bd3c2
4 files changed
+70 -3

No files matched your search

+11 -2
View File
@@ -4,6 +4,10 @@ Hermes is the self-improving AI agent from Nous Research. It runs in a terminal,
**Host:** Dankclaw — **Hostname:** `hermes.dankclaw.local` — **Docs:** https://hermes-agent.nousresearch.com/docs
**Persistent state:** `/home/dank/hermes-data` on Dankclaw, mounted as `/data` in
both containers. The tracked, sanitized configuration baseline is
[`dankclaw/hermes/config.yaml.example`](../../dankclaw/hermes/config.yaml.example).
## Facts (from research, primary source)
| Item | Value |
@@ -17,15 +21,20 @@ Hermes is the self-improving AI agent from Nous Research. It runs in a terminal,
## Configuration
- Point Hermes at the local model endpoint (`http://localhost:7770/v1`) or an external provider through its provider config.
- Point Hermes at the local model endpoint or an external provider through its provider config.
- The gateway process exposes one port for chat integration; the exact port is set in the Hermes config (`8090` convention in this repo).
- The data volume persists skills, memory, and session history.
- The configured `dankserver-small` provider reaches `http://192.168.0.235:7770/v1`
and exposes the `frank-default-small` alias. It is a named provider, so it can
coexist with the existing `custom` provider for the large model.
- The live `config.yaml` contains secrets and user state and is not committed;
the tracked example is the sanitized backup of its non-secret settings.
## Volumes
| Container path | Host path (convention) |
|----------------|------------------------|
| `/data` | `/opt/hermes/data` |
| `/data` | `/home/dank/hermes-data` |
## Gotchas