Cairn

Review fork tool inheritance and cache parity bug

NousResearch/hermes-agent · cluster 103579

Data as of

Nothing open on GitHub. Fix merged in #105843. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #105843. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #105843. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and PRs concern a bug where background review forks do not properly inherit the parent agent's full tool surface, causing tools[] cache parity problems. Multiple fix attempts address copying parent tools onto the review fork.

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.

  • #105843 Background-review fork advertises the parent's exact tools[] and keeps it through compaction (#103579, salvage #103581)

    merged to main

    files: agent/background_review.py, contributors/emails/[redacted:email], tests/run_agent/test_background_review_cache_parity.py

3 PRs closed without merging

From the close comments: duplicate 2 · merged via another change 1

  • #103581 fix(agent): inherit parent's full tool surface on review fork for cache parity (#103579) · merged via another change → cb4c73d, fccff8a, 6149b1d, #105843
  • #103666 fix(agent): inherit the parent's full tool surface on the review fork (#103579) · duplicate → #103581
  • #103937 fix(agent): copy parent tools onto same-model review fork · duplicate → #103581, #103579
Closed issues · 1
  • Closed#103579[Bug]: background_review fork drops external memory-provider tools, breaking tools[] cache parity
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.40: 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
#105843
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
9 Sep 2026

For your agent

The same facts, typed.

cluster/103579.json
cluster/103579.md