NousResearch/hermes-agent

Unreadable ticket wedging bot delivery pipeline

Cluster 109820. Data as of 2026-10-24 04:06 UTC

Nothing open on GitHub. Fix merged in #113405 on 16 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #113405. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #113405. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #113405 Pick up a Lab task

A bug where a single unreadable ticket file causes the entire bot live delivery pipeline to stall, resulting in ambiguous errors for senders and a crashed receiver poller. The members cover the bug report and related fix attempts across tools and bot-mode delivery.

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.

#113405 fix(bot-mode): one unreadable mailbox ticket no longer wedges teammate DM delivery (#109820, salvage #109830)

merged to main

files: apps/desktop/e2e/bot-mailbox-unreadable-ticket.spec.ts, cron/bot_chat_delivery.py, tests/cron/test_bot_chat_pending.py, tests/tools/test_bot_live_owner_delivery.py, tools/bot_live_delivery.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · duplicate 1

#109830 fix(tools): stop one unreadable ticket from wedging bot live delivery · done elsewhere → c3f0d87, #113405, #10982
#109878 fix(tools): one unreadable ticket no longer wedges bot live delivery · duplicate → #109830

Closed issues · 1

Closed#109820[Bug]: one unreadable ticket file wedges the whole bot_live_delivery pipeline (senders get 'ambiguous', receiver poller crashes)

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

Merged PRs: #113405
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 16 Sep 2026

For your agent

The same facts, typed.

cluster/109820.json
cluster/109820.md