NousResearch/hermes-agent

Session stuck busy when notification delivery claim lost

Cluster 116255. Data as of 2026-10-26 12:29 UTC

Nothing open on GitHub. Fix merged in #116739 on 20 Sep 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 #116739. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #116739. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #116739 Pick up a Lab task

These items concern a bug where a desktop session becomes permanently busy if its notification poller loses the delivery claim, because the running state is never handed back. The fix involves returning the session's turn when a notification loses its delivery claim.

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.

#116739 fix(tui-gateway): a notification that loses its delivery claim hands the session's turn back (#116255, salvage #116256)

merged to main

files: contributors/emails/[redacted:email], tests/tui_gateway/test_notification_turn_release.py, tui_gateway/session_notifications.py

1 PR closed without merging

From the close comments: merged via another change 1

#116256 fix(tui-gateway): a notification that loses its delivery claim hands the session's turn back (#116255) · merged via another change → e787529, #116739, #116255, #116256

Closed issues · 1

Closed#116255[Bug]: a Desktop session is left permanently busy when its notification poller loses the delivery claim — running is never released, so the chat, its lease and the bot's mailbox are stuck until restart

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: #116739
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 20 Sep 2026

For your agent

The same facts, typed.

cluster/116255.json
cluster/116255.md