Cairn

Same-model review fork cache scope inheritance fixes

NousResearch/hermes-agent · cluster 109964

Data as of

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

The short answer

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

Multiple fixes and attempts addressing a bug where same-model background review forks resolve to a different cache scope than their parent gateway. The work focuses on ensuring review forks correctly inherit or match the parent's cache bucket/scope.

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.

  • #110867 fix(agent): same-model background review lands in its parent's cache bucket (#109964, salvage #110009 + #110045)

    merged to main

    files: agent/background_review.py, agent/prompt_cache_scope.py, run_agent.py, tests/agent/test_background_review_cache_parity.py

4 PRs closed without merging

From the close comments: done elsewhere 2 · merged via another change 1 · superseded by another PR 1

  • #110009 fix(agent): same-model review fork inherits the parent's resolved cache scope (#109964) · merged via another change → a4b620f, 6bc0e9e, #110867, #110045
  • #110017 fix(agent): inherit parent cache scope on same-model review forks · superseded by another PR
  • #110045 fix(agent): complement review cache scope with conversation root and gateway key parity (#109964) · done elsewhere → 6bc0e9e, a4b620f, #110867, #110009
  • #110048 fix(review): let a same-model fork route on its parent's cache scope · done elsewhere → #110009, #110045
Closed issues · 1
  • Closed#109964Same-model background review can resolve a different cache scope than its gateway parent
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.33: 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
#110867
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
14 Sep 2026

For your agent

The same facts, typed.

cluster/109964.json
cluster/109964.md