# NousResearch/hermes-agent · Provider timeout config in streaming API calls, plus bundled items

## Open now

- Nothing open on GitHub.

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.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #27550. Verify it addresses your case.
- **Recommended:** read PR #27550 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

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

## Prior & competing PRs

- **#27550: Batch salvage group 6 (final): streaming timeout config + docker exit-75 restart + dashboard loopback/base-path**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - 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`
- **#25260: fix(agent): honor provider timeout config in streaming API calls**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#27550`

## Fix status

- Merged to main in PR #27550 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-05-17`.