Hermes Agent

Hermes Agent is an agent framework covering multi-step tool calls, browser automation, code execution and file operations. It speaks the OpenAI protocol.

Recommended: let CC Switch do it#

CC Switch supports Hermes Agent — add a provider with https://gateway.amux.ai/v1 as the Base URL. Open a fresh terminal after switching.

The manual route is below.

1. Create an Amux key#

Create one on the keys page in the console. The key remains viewable there after creation, so you do not need to rotate it just to retrieve it again.

2. Run the wizard#

hermes model

It is interactive; there is no file to edit. Pick the custom endpoint option, then fill in:

Keep the /v1: OpenAI-family clients append /chat/completions directly.

3. Where the answers land#

The wizard writes to ~/.hermes/config.yaml, with provider set to custom and base_url pointing at that address. Open that file when you need to check what is in effect.

4. Check it works#

Start Hermes Agent and give it a small task that requires a tool, such as reading the README in the current directory and summarizing it. Because Hermes Agent relies heavily on tool calls, a plain text message is not enough to verify the full path.

Choosing models#

Run hermes model again.

Names are canonical IDs and are not limited to OpenAI's models. Hermes Agent depends heavily on tool calls, so check the capabilities listed on each model page; models with weak tool support typically cannot complete agent-style tasks reliably.

To pin a provider or choose a routing strategy, append a colon (anthropic/claude-opus-5:@reliability) — see the API reference. :@reliability is worth trying for long runs: it prefers providers with a high success rate, and failing halfway costs far more in an agent than a slightly slower first token.

Troubleshooting#

Authentication failure#

Was the key copied in full? Is it still enabled in the console? Does the workspace have balance? Also confirm the Base URL keeps the /v1 — an address one segment short also surfaces as an auth-style error.

Configuration changes have no effect#

Open a fresh terminal. You can also read ~/.hermes/config.yaml directly and confirm provider is custom and base_url is what you entered.

Tool calls keep failing#

This is usually model-related rather than a configuration issue. Try a model with stronger tool-calling support; each model page lists its capabilities.

A long run stops partway#

Use the :@reliability suffix so routing prefers providers with a high success rate. Also check the workspace balance: running out mid-run fails the request after the agent has already done a lot of work.