NousResearch/hermes-agent
Google Chat cron messages threading incorrectly as replies
Cluster 84324. Data as of
Nothing open on GitHub. Fix merged in #84328 on 13 Aug 2026. Check it covers your case.
The short answer
0open issues
0open PRs
3items grouped
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #84328. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #84328. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where scheduled cron deliveries in Google Chat appear as replies to the last active thread rather than starting new top-level threads. Two fixes address this by adjusting delivery behavior and skipping a fallback mechanism for cron messages.
Open issues0
Open PRs0
Fixes on record
-
#84328 fix(google-chat): post cron deliveries as new top-level threads, not replies
files:
plugins/platforms/google_chat/adapter.py,tests/gateway/test_google_chat.py
1 PR closed without merging
From the close comments: duplicate 1
-
#84338 fix(gateway): skip _last_inbound_thread fallback for cron deliveries in Google Chat · duplicate →
#84328
Closed issues · 1
- Closed#84324[Bug]: Google Chat cron deliveries land as replies in the last active thread instead of a new top-level thread
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.00means 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 LabAt a glance
- Merged PRs
- #84328
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 13 Aug 2026