NousResearch/hermes-agent

Bot-relay turn booking vs handoff kill bug

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

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

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

Read #116968 Pick up a Lab task

These items concern a bug where a relayed turn's completion is incorrectly treated as a delivery timeout and killed alongside its handoff, rather than being booked from its own turn report. The fixes address how lingering relayed turns at the cap are handled separately from their handoff lifecycle.

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.

#116968 fix(bot-relay): a relayed turn still lingering at the cap is booked from its turn report, not killed with its handoff (#114980, salvage #115312)

merged to main

files: cli.py, cron/scheduler_delivery.py, hermes_cli/quiet_single_query.py, tests/hermes_cli/test_quiet_single_query.py, tests/tools/test_bot_retry_policy.py, tests/tools/test_bot_turn_lock.py, tests/tui_gateway/test_bot_relay_methods.py, tui_gateway/methods_bot_relay.py, website/docs/user-guide/bot-mode.md

1 PR closed without merging

From the close comments: done elsewhere 1

#115312 fix(bot-relay): a relayed turn is booked from its turn report at the cap, not killed with its handoff (#114980) · done elsewhere → #116968, #114980

Closed issues · 1

Closed#114980[Bug]: relayed DM shares one 600s deadline between the turn and the exit linger — a completed turn is booked as delivery_timeout, its reply lost and its handoff killed

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

For your agent

The same facts, typed.

cluster/114980.json
cluster/114980.md