Cairn
NousResearch/hermes-agent

Configurable WebSocket write timeout via env var

Cluster 51288 · dashboard. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 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
Nothing open on GitHub.

These members all concern adding support for configuring the WebSocket write timeout in the TUI through an environment variable, tentatively named HERMES_TUI_WS_WRITE_TIMEOUT_S. The group includes a feature request, a fix, and a feature implementation addressing the same capability.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: duplicate 1 · other 1

  • #51860 feat(tui): make WebSocket write timeout configurable via env var · other → ebb81f1, #51288
  • #52041 fix(tui): make websocket write timeout configurable · duplicate → #51860, #51288
Closed issues · 1
  • Closed#51288Feature Request: Add HERMES_TUI_WS_WRITE_TIMEOUT_S environment variable
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

Subsystem
dashboard
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/51288.json
cluster/51288.md