NousResearch/hermes-agent

PTY session reaping blocked by attach/socket errors

Cluster 110849 · dashboard. Data as of

2 open items. Fix merged in #111357 on 15 Sep 2026. Check it covers your case.

The short answer

0open issues
2open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #111357. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #111357. That is separate from the fix event.
Still open
0 issues and 2 PRs.

Several fixes address scenarios where erroring or dropped WebSocket attachments leave PTY sessions permanently marked as attached, preventing idle reaping from reclaiming them. The changes cover socket send errors, mid-replay drops, and commit-ordering issues in the attach lifecycle — including a case where PtySession.attach() commits attached state before the replay write, leaving the PTY permanently unreapable if a client drops during attach.

Open issues0

No open issues.

Open PRs2

  • PR#110861fix(dashboard): roll back a mid-replay attach drop so idle reaping can reclaim the PTY
  • PR#110863fix(pty): make failed websocket attachments reapable

Fixes on record

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

  • #111357 fix(dashboard): dropped terminal viewers no longer pin the PTY as attached forever (#110849, salvage #110859)

    merged to main

    files: hermes_cli/pty_session.py, hermes_cli/web_routers/chat_ws.py, tests/hermes_cli/test_pty_session.py

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #110859 fix(pty): recover sessions after socket send failures · superseded by another PR → #111357
Closed issues · 1
  • Closed#110849PtySession.attach() commits attached state before the replay write — a client dropping during attach leaves the PTY permanently unreapable
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.40: 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
Merged PRs
#111357
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
15 Sep 2026

For your agent

The same facts, typed.