NousResearch/hermes-agent

Bot relay refusal reasons missing typed data

Cluster 113532. Data as of 2026-10-24 13:18 UTC

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

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

Read #114955 Pick up a Lab task

These issues and PRs concern a bug where relay delivery refusals (such as target_busy and delivery_timeout) lose their typed reason field in transit, arriving at the sender as 'unknown'. The work focuses on ensuring the reason is correctly carried through the refusal delivery path.

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.

#114955 fix(bot-relay): target_busy and delivery_timeout relay refusals reach the sender with their typed reason (#113532, salvage #113534)

merged to main

files: tests/tools/test_bot_turn_lock.py, tools/bot_failure_reasons.py, tools/bot_mode_dm.py, tui_gateway/methods_bot_relay.py

2 PRs closed without merging

From the close comments: duplicate 1 · merged via another change 1

#113534 fix(bot-relay): every deliver refusal carries its typed reason, not just a JSON-RPC code · merged via another change → 2d773ff, #114955, #113532, #113534
#113602 fix(bot-relay): carry typed reasons through delivery refusals · duplicate → #113534, #113532

Closed issues · 1

Closed#113532Relay delivery refusals ship no data.reason, so target_busy and delivery_timeout reach the sender as 'unknown'

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: #114955
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 18 Sep 2026

For your agent

The same facts, typed.

cluster/113532.json
cluster/113532.md