Cairn
NousResearch/hermes-agent

Memory context repetition and SQLite performance work

Cluster 117397. Data as of

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

The short answer

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

These items concern a performance problem where recalled lines are repeated within memory-context blocks and replayed on every subsequent request, along with related SQLite connection overhead. The work addresses stating each recalled line only once per block and scoping capability epoch checks to exclude archived skills.

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.

  • #118962 perf: one SQLite connection per delivered reply, memory-context bullets stated once, capability epoch ignores archived skills (salvage #117399, #117789, #117951)

    merged to main

    files: agent/memory_manager.py, gateway/delivery_ledger.py, tests/agent/test_memory_context_dedupe.py, tests/gateway/test_delivery_ledger.py, tests/gateway/test_delivery_ledger_single_connection.py, tests/tools/test_capability_fingerprint_skill_scope.py, tools/bot_mode_probe.py

1 PR closed without merging

From the close comments: done elsewhere 1

  • #117399 perf(memory): a recalled line is stated once per memory-context block · done elsewhere → 28bd8cc, 83a1a9a, cbe23de, 2bade5d, a48dde5, aca4dc8, #118962
Closed issues · 1
  • Closed#117397[Perf]: the per-turn <memory-context> block repeats recalled lines, and every repeat is replayed on every later request
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
#118962
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
22 Sep 2026

For your agent

The same facts, typed.

cluster/117397.json
cluster/117397.md