Normalize Hermes local provider names

2026-08-25 19:42:46 -07:00
parent 8fb5bd7a5a
commit 4308f62004
2 changed files with 12 additions and 8 deletions
@@ -24,9 +24,10 @@ both containers. The tracked, sanitized configuration baseline is
 - 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.
+- Hermes has two named local providers: `dankclaw-large` reaches
+  `http://192.168.0.143:7770/v1` and exposes `frank-default-large`;
+  `dankserver-small` reaches `http://192.168.0.235:7770/v1` and exposes
+  `frank-default-small`.
 - 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.