hermes - 💡(How to fix) Fix [Feature]: configurable default headers / User-Agent for third-party API [1 participants]

Problem or Use Case

Many third-party API relays are placed behind Cloudflare, whose WAF often intercepts and blocks requests with default or missing User-Agents. Currently, Hermes instantiates OpenAI-compatible clients directly in code (e.g., OpenAI(api_key=..., base_url=...)), leaving no supported way to inject custom headers like a custom User-Agent to bypass these Cloudflare restrictions. This forces users to modify the source code or deploy an additional reverse proxy, which is far from ideal.

Proposed Solution

Expose an optional config field for default headers, for example: yaml model: base_url: https://example.com/v1 api_key: sk-... default_headers: User-Agent: HermesAgent/1.0 X-Client-Name: Hermes Implementation idea:

• pass default_headers=... when constructing coustom
• support the same for custom endpoint paths and other OpenAI-compatible client creation points
• merge user headers with provider defaults; user config should win on conflicts

Alternatives Considered

• patching the source code
• adding a local reverse proxy to inject headers
• using environment-specific hacks

These work, but a built-in config option would be cleaner and easier to maintain.

Feature Type

Gateway / messaging improvement

Scope

Small (single file, < 50 lines)

Contribution

• I'd like to implement this myself and submit a PR

Debug Report (optional)