NousResearch/hermes-agent

Provider timeout config in streaming API calls, plus bundled items

Cluster 25249. Data as of 2026-10-27 11:58 UTC

Nothing open on GitHub. Fix merged in #27550 on 17 May 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #27550. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #27550, then check it covers your case.

Read #27550 Pick up a Lab task

Two members concern timeout settings (stale_timeout_seconds and HERMES_API_CALL_STALE_TIMEOUT) apparently not being honored in streaming API calls, with one reporting a hardcoded 30s timeout. The third is a batch grouping that mentions the streaming timeout config alongside unrelated docker exit-75 restart and dashboard loopback/base-path work.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#27550 Batch salvage group 6 (final): streaming timeout config + docker exit-75 restart + dashboard loopback/base-path

merged to main

files: agent/chat_completion_helpers.py, gateway/run.py, hermes_cli/web_server.py, scripts/release.py, web/src/components/ChatSidebar.tsx, web/src/lib/gatewayClient.ts, web/src/pages/ChatPage.tsx

1 PR closed without merging

From the close comments: merged via another change 1

#25260 fix(agent): honor provider timeout config in streaming API calls · merged via another change → #27550

Closed issues · 1

Closed#25249custom provider: stale_timeout_seconds and HERMES_API_CALL_STALE_TIMEOUT are ignored — hardcoded 30s timeout

How this cluster was grouped

Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Merged PRs: #27550
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 17 May 2026

For your agent

The same facts, typed.

cluster/25249.json
cluster/25249.md