Skip to content

fix(memory): increment retrieval_count on search results in holographic memory (#17899)#39664

Open
dusterbloom wants to merge 1 commit into
NousResearch:mainfrom
dusterbloom:fix/holographic-retrieval-count
Open

fix(memory): increment retrieval_count on search results in holographic memory (#17899)#39664
dusterbloom wants to merge 1 commit into
NousResearch:mainfrom
dusterbloom:fix/holographic-retrieval-count

Conversation

@dusterbloom

Copy link
Copy Markdown
Contributor

Fixes #17899

FactRetriever.search() bypassed store.search_facts(), the only place that bumped retrieval_count. The counter was always 0.

Fix: Increment retrieval_count directly in FactRetriever.search() for returned facts, with silent error handling.

Tests: 3 tests — increments on search, accumulates across multiple searches, unrelated facts stay at 0.

This was originally part of #23221 — split into focused single-fix PRs for easier review.

…ic memory (NousResearch#17899)

FactRetriever.search() bypassed store.search_facts(), the only place
that bumped retrieval_count. The counter was always 0.

Fix: increment retrieval_count directly in FactRetriever.search() for
returned facts, with silent error handling.

Closes NousResearch#17899
@alt-glitch alt-glitch added type/bug Something isn't working P3 Low — cosmetic, nice to have comp/plugins Plugin system and bundled plugins tool/memory Memory tool and memory providers labels Jun 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp/plugins Plugin system and bundled plugins P3 Low — cosmetic, nice to have tool/memory Memory tool and memory providers type/bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[bug] Holographic memory: retrieval_count never incremented — search() in retrieval.py bypasses store.search_facts()

2 participants