hermes - 💡(How to fix) Fix custom_providers with anthropic_messages mangles dotted model names → 502 from local proxies [4 comments, 3 participants]

Environment

• Hermes version: v0.11.0 (2026.4.23) (note: my install is 154 commits behind, but the affected code is unchanged on main as of ff687c019 — see line 8023 in run_agent.py)
• OS: macOS 15.4
• Setup: local proxy (CCS / cliproxy) at http://127.0.0.1:8317 translating Anthropic API → Codex backend

Problem

When configuring a custom_provider that uses api_mode: anthropic_messages, dots in the model name are silently replaced with hyphens before the request is sent. This breaks any local/self-hosted proxy that expects the model name to be passed through verbatim (e.g. gpt-5.4, glm-4.6, etc.).

Repro

~/.hermes/config.yaml:

model:
  default: gpt-5.4
  provider: codex

custom_providers:
- name: codex
  base_url: http://127.0.0.1:8317/api/provider/codex
  api_key: ccs-internal-managed
  api_mode: anthropic_messages
  model: gpt-5.4

Outgoing request body (captured at the proxy):

{ "model": "gpt-5-4", ... }

Proxy responds 502 {"error":{"message":"unknown provider for model gpt-5-4"}}, Hermes retries 3× then falls back.

Root cause

_anthropic_preserve_dots() in run_agent.py (line 8023 on main) gates dot-preservation on a hardcoded provider/base_url allowlist:

if (getattr(self, "provider", "") or "").lower() in {
    "alibaba", "minimax", "minimax-cn",
    "opencode-go", "opencode-zen",
    "zai", "bedrock",
}:
    return True
base = (getattr(self, "base_url", "") or "").lower()
return (
    "dashscope" in base
    or "aliyuncs" in base
    or "minimax" in base
    or "opencode.ai/zen/" in base
    or "bigmodel.cn" in base
    or "bedrock-runtime." in base
)

A user-defined custom_provider pointing at 127.0.0.1 / localhost / a private domain will never match, so normalize_model_name() falls back to model.replace(".", "-").

Workaround (local patch)

Adding 127.0.0.1 and localhost to the base_url allowlist works for my case, but it's not a general solution — some users may genuinely want the dot→hyphen behavior on their local proxy.

Proposed fix — would like maintainer guidance

Two options, would like to know which you prefer before opening a PR:

1. URL allowlist extension (minimal): treat 127.0.0.1, localhost, and any host that resolves to a private/loopback range as dot-preserving by default. ~5 LoC.

2. Config-driven (more general): add an explicit preserve_model_dots: bool field on custom_providers entries, defaulting to false for backward compat. Lets users opt in regardless of host.

   custom_providers:
   - name: codex
     base_url: http://127.0.0.1:8317/api/provider/codex
     api_mode: anthropic_messages
     preserve_model_dots: true

Happy to send a PR for whichever approach you'd like.