# NousResearch/hermes-agent · Reduce SQLite connections during message delivery

## Open now

- Nothing open on GitHub.

These items address excessive SQLite connection usage in the delivery ledger, where sweeps and retention checks were triggering multiple database connections per delivered message. Work involves bounding sweep frequency and consolidating connection overhead.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #118962. Verify it addresses your case.
- **Recommended:** read PR #118962 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-118962`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #117949: Delivery ledger sweeps retention on every reply — 4 SQLite connections per delivered message

## Prior & competing PRs

- **#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 · fix tier `verified`
  - maintainer direction: category `merged`
  - 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`
- **#117951: perf(gateway): sweep the delivery ledger on a bound, not on every reply**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `28bd8cc08c`, `#118962`

## Fix status

- Merged to main in PR #118962 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-22`.