NousResearch/hermes-agent

Agent background review transcript isolation fixes

Cluster 100795. Data as of 2026-10-24 04:06 UTC

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

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

Read #101074 Pick up a Lab task

A cluster of bug fixes addressing how the agent handles transcript and wire-byte state during background review forks, preventing payload divergence that degraded cache prefix hit rates after agent close or review cycles.

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.

#101074 fix(agent): background review fork gets a structural transcript clone, not a shallow list (salvage #100802)

merged to main

files: agent/turn_finalizer.py, run_agent.py, tests/agent/test_refine_snapshot_isolation.py, tests/run_agent/test_background_review.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

#100802 fix(agent): isolate background review transcript snapshots · merged via another change → #101074
#100839 fix(agent): persist the wire bytes any reload rewrite would drop · done elsewhere → 261a4ef, fcd5bbb, #100795, #100802, #100159

Closed issues · 1

Closed#100795[Bug]: State-rebuild payload divergence — after agent close / background review, the next user turn's API request no longer matches the cached prefix (0–85% hit for one shot)

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

For your agent

The same facts, typed.

cluster/100795.json
cluster/100795.md