NousResearch/hermes-agent

prefix cache preservation across compaction rebuilds

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

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

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

Read #104455 Pick up a Lab task

These items address how the prefix cache and prompt prefix are maintained during memory compaction rebuilds, including pinning workspace snapshots and MEMORY blocks to reduce cache loss across sessions.

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.

#104455 Compaction rebuilds keep the prefix cache in coding sessions: the workspace snapshot is pinned per session instead of re-probed (#103326, salvage of #103358 by @JoaoMarcos44)

merged to main

files: agent/agent_init.py, agent/coding_context.py, agent/system_prompt.py, run_agent.py, tests/test_compaction_prompt_rebuild.py, tui_gateway/methods_session.py

2 PRs closed without merging

From the close comments: merged via another change 2

#103358 perf(prefix-cache): pin session-start workspace snapshot across compaction rebuilds · merged via another change → #104455, #103331, #103566, #103326
#103566 fix(agent): preserve the prompt prefix across memory reloads · merged via another change → f58fcc8, #103331

Closed issues · 1

Closed#103326perf(prefix-cache): pin built-in MEMORY block at the end of the volatile band to cap compaction-rebuild cache loss

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

For your agent

The same facts, typed.

cluster/103326.json
cluster/103326.md