hermes - 💡(How to fix) Fix openai-codex / gpt-5.5 consistently timing out on this instance

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Fix Action

Temporary workaround

Switched primary model to a different provider (mimo-v2.5-pro via custom), which resolves the issue immediately. Same context size, same workload, no timeouts.

RAW_BUFFERClick to expand / collapse

What happened

When using openai-codex / gpt-5.5 as the primary model, requests frequently stall until the 90s stale timeout is hit, then retry and stall again. A single simple message ("报数") took 401.8s to get a response — 5 API calls, 4 of them hitting the 90s stale limit.

Other servers calling the same openai-codex / gpt-5.5 respond quickly (3-7s). Network latency to chatgpt.com is fine (~0.32-0.39s TLS).

Observed pattern

Not every request is slow — it is fast-slow alternating:

  • Fast: 3.1s, 4.4s, 5.3s, 6.5s, 7.1s
  • Slow: 96.8s, 98.4s, 99.2s, 103.2s, 150.2s, 208.6s, 290.2s

Input context was ~24k-28k tokens per retry (no growth between retries).

Environment

  • Hermes Agent v0.14.0
  • macOS (Mac Mini)
  • Provider: openai-codex / gpt-5.5 via chatgpt.com/backend-api/codex
  • ~20 active sessions, ~24 cron jobs concurrent
  • Telegram gateway

The question

Is this a compatibility issue between Hermes and the openai-codex backend? Or is it purely a provider-side issue? Not sure — but other servers using the same model do not show this behavior.

Temporary workaround

Switched primary model to a different provider (mimo-v2.5-pro via custom), which resolves the issue immediately. Same context size, same workload, no timeouts.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Temporary workaround

Switched primary model to a different provider (mimo-v2.5-pro via custom), which resolves the issue immediately. Same context size, same workload, no timeouts.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING