NousResearch/hermes-agent

Bot-chat cron delivery timeout booking fix

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

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

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

Read #114898 Pick up a Lab task

These items concern a bug where bot-chat delivery incorrectly booked a completed turn with a 600-second linger timeout, and related fixes to ensure the bot's turn is booked correctly rather than its exit linger.

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.

#114898 fix(cron): bot-chat delivery books the bot's turn, not its exit linger — no more 600s timeouts on completed turns (#113608, supersedes #113649)

merged to main

files: cli.py, cron/scheduler_delivery.py, hermes_cli/quiet_single_query.py, tests/cron/test_bot_chat_cli_home.py, tests/cron/test_bot_chat_pending.py, tests/cron/test_bot_chat_pending_identity.py, tests/cron/test_bot_chat_warning_replay.py, tests/cron/test_cron_bot_chat_delivery.py, tests/cron/test_cron_live_bot_delivery.py, tests/hermes_cli/test_quiet_single_query.py, website/docs/user-guide/features/cron.md

1 PR closed without merging

From the close comments: superseded by another PR 1

#113649 fix(cron): reserve bot chat completion linger · superseded by another PR → 4ce832e, #114898, #113608, #113649

Closed issues · 1

Closed#113608cron: bot-chat delivery books a completed turn as a 600s timeout (linger bound == delivery cap, so the cap always loses)

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

For your agent

The same facts, typed.

cluster/113608.json
cluster/113608.md