NousResearch/hermes-agent

Background review context rejection handling fixes

Cluster 114644. Data as of 2026-10-26 12:29 UTC

Nothing open on GitHub. Fix merged in #114870 on 19 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

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

Read #114870 Pick up a Lab task

These items relate to how background review context failures are detected and reported, specifically addressing cases where a context rejection from background review was incorrectly attributed to the foreground conversation being too long. Changes also involve budget adjustments for local models.

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.

#114870 fix(review, agent): background-review budget fits local models; server context rejection no longer blamed on the conversation (#114645, #114644, salvage #114651)

merged to main

files: agent/background_review.py, agent/turn_failure_copy.py, agent/turn_overflow.py, contributors/emails/[redacted:email], hermes_cli/config_defaults.py, tests/agent/test_background_review_input_budget.py, tests/agent/test_failed_turn_site_codes.py, website/docs/reference/faq.md, website/docs/user-guide/features/memory.md

1 PR closed without merging

From the close comments: superseded by another PR 1

#114649 fix(agent): distinguish background review context failures · superseded by another PR → 1baae31, #114870, #114645, #114644, #114651

Closed issues · 1

Closed#114644[Bug]: Background-review context rejection is reported as the foreground conversation being too long

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.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: #114870
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 19 Sep 2026

For your agent

The same facts, typed.

cluster/114644.json
cluster/114644.md