Hermes keeps several providers at once and stores them in config.yaml under
its default directory ~/.hermes. OcHub can also manage its MCP servers and
skills. Hermes may be disabled by default; enable it under Settings → Apps
and plugins before opening its page.
Configure a custom connection
-
Choose an API mode:
Mode Upstream chat_completionsOpenAI-compatible Chat anthropic_messagesClaude Messages codex_responsesOpenAI Responses bedrock_converseAWS Bedrock Converse -
Enter Base URL and API key.
-
Add models. The first model ID also becomes the runtime and
/modeldefault. -
Add optional display names and context lengths.
-
Use
rate_limit_delayfor a required delay between calls. -
Review the generated
config.yaml, save, and restart Hermes.
Without an explicit mode, Hermes treats a provider as Chat Completions, so Anthropic, Responses, and Bedrock upstreams must select the matching mode.
Model and memory maintenance
Under Advanced tools → Hermes model and memory, you can:
- Read and save the
modelnode inconfig.yaml. - Edit MEMORY and USER memory content.
- Toggle each memory type.
- Inspect character counts and enabled state.
Do not edit while a running Hermes agent is writing memory. Record any backup path shown after a save or toggle.
After saving, follow the verification checklist to confirm the new connection works.

