hermes - 💡(How to fix) Fix OmniRoute compatibility: local custom providers can stall indefinitely on streamed chat completions [1 participants]

Hermes requests routed through a local custom provider can appear to hang indefinitely, especially for commands like hermes changelog last commits 33.

This is best understood as an OmniRoute compatibility issue because the affected requests are being sent through a local OmniRoute endpoint. For reference, the OmniRoute repository is:

• https://github.com/diegosouzapw/OmniRoute

Observed behavior:

• provider=custom
• base_url=http://localhost:20128/v1 (OmniRoute)
• streamed chat-completions path uses the 1800s fallback request timeout
• stream-stale detection is disabled for local endpoints
• no default max_tokens is applied for custom providers, so output is effectively unbounded unless the caller sets one explicitly

Impact:

• the CLI/TUI can sit on one request for a very long time with no visible progress
• the request looks stalled even when OmniRoute is healthy

Proposed fix:

• use a finite default timeout for local custom providers
• keep stream-stale detection finite for local custom providers
• apply a conservative default output cap when max_tokens is unset

I have a local patch for this behavior in run_agent.py and agent/transports/chat_completions.py.