More Agents
Hermes
Quick answer
Prism inserts a marked region under the top-level
providers:key in Hermes's config.yaml, holding prism for Chat Completions models and prism-responses for Responses models, each listing only the models it can serve.Last updated Reviewed against Prism v0.3.26
Config location
| Platform | Path |
|---|---|
| Windows | %LOCALAPPDATA%\hermes\config.yaml |
| macOS | ~/.hermes/config.yaml |
| Linux | ~/.hermes/config.yaml |
One-click setup
1
Open the Agents tab
In the Admin UI, select
Agents, then Hermes.2
Click Setup
Prism strips its previous region and inserts a fresh one, keeping a one-time backup of the original YAML.
3
Select a Prism provider
Both Prism providers appear in Hermes's provider picker with their models listed.
What Prism writes
providers:
# >>> prism providers managed >>>
prism:
api: http://127.0.0.1:11434/v1
api_key: prism
transport: chat_completions
default_model: "glm-5.1:cloud"
models:
"glm-5.1:cloud":
context_length: 128000
max_output_tokens: 16384
prism-responses:
api: http://127.0.0.1:11434/v1
api_key: prism
transport: codex_responses
default_model: "gpt-5.2-codex"
models:
"gpt-5.2-codex":
context_length: 128000
# <<< prism providers managed <<<Fields Prism sets
| Key | Value |
|---|---|
| api | The Prism proxy's OpenAI-compatible base. |
| api_key | The fixed Prism token. |
| transport | chat_completions for the prism provider, codex_responses for prism-responses. |
| default_model | The first model on that provider, so the entry is usable immediately. |
| models.<id>.context_length | The model's context length, defaulting to 128000. |
| models.<id>.max_output_tokens | Written only when the model declares a max output. |
Transport is a per-provider property in Hermes, which is why chat and Responses models are split across two entries. A provider entry with no models is omitted entirely.
How the managed region works
Prism's region is delimited by comment markers # >>> prism providers managed >>> and # <<< prism providers managed <<<. On each sync the old region is removed wherever it appears in the file and a new one is inserted under providers:, so re-syncing never duplicates entries and never disturbs your own keys.
Two independent regions
Hermes keeps both providers and MCP servers in one YAML file, so Prism maintains two separate marked regions there. Disabling the provider integration removes only the providers region, leaving MCP intact — and vice versa.
Add MCP servers
Hermes stores MCP servers in mcp_serversin the same file. Enabling Hermes in the MCP tab inserts a second marked region with Prism's gateway. See MCP Gateway.