NousResearch/hermes-agent

HTTP client timeout and IPv4 networking fixes

Cluster 37662 · agent. Data as of

1 open item. Fix attempted, not merged.

The short answer

0open issues
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
0 issues and 1 PR.

These items address two related networking issues in the agent HTTP client: adding explicit timeouts to prevent indefinite hangs, and ensuring the force_ipv4 setting is respected during agent and CLI bootstrap. A related report describes connection hangs on IPv6 endpoints.

Open issues0

No open issues.

Open PRs1

  • PR#37818fix: honor force_ipv4 in run_agent and legacy cli bootstrap

2 PRs closed without merging

From the close comments: other 2

  • #37898 fix(agent): add explicit httpx timeout to keepalive HTTP client (#37662) · other → 8324dd1, 51c1ba6
  • #82634 fix: honor network.force_ipv4 on run_agent and legacy cli bootstrap · other
Closed issues · 1
  • Closed#37662httpx/OpenAI SDK hangs on IPv6 when connecting to provider endpoints (e.g. opencode.ai) — suggest happy-eyeballs fix
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.50: 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

Subsystem
agent
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.