Fix skipped assistant reply after consecutive review prompts
Cluster 110606. Data as of
Nothing open on GitHub. Fix merged in #111566 on 15 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #111566. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #111566. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These members address a bug where consecutive background-review harness messages caused the subsequent real assistant reply to be incorrectly dropped during state restoration. The fix ensures assistant replies are preserved in that scenario.
Open issues0
Open PRs0
Fixes on record
-
#111566 fix(state): consecutive background-review prompts no longer drop the real assistant reply on restore (#110606, salvage #110618)
files:
hermes_state.py,tests/hermes_state/test_background_review_session_isolation.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#110618 fix(state): preserve replies after consecutive review harness prompts · merged via another change →
#111566
Closed issues · 1
- Closed#110606[Bug] _strip_background_review_harness skips next assistant incorrectly on consecutive harness messages
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
- #111566
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 15 Sep 2026