---
title: "Discussion on \"Agent memory needs more than vector search\" | Hashnode"
description: "Discussion on \"Agent memory needs more than vector search\". Vector search is great, but it only goes so far. I benchmarked several ways to improve relevance with surprising results."
url: "https://hashnode.com/posts/agent-memory-needs-more-than-vector-search/6abbcc77cb659b470c8d2d80"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Agent memory needs more than vector search](https://allenheltondev.hashnode.dev/agent-memory-needs-more-than-vector-search?utm_source=hashnode&utm_medium=feed)

Vector search is great, but it only goes so far. I benchmarked several ways to improve relevance with surprising results.

Sep 29 · 12 min read · allenheltondev.hashnode.dev  
Read the article

-   [#ai](https://hashnode.com/tag/ai)
-   [#ai-agents](https://hashnode.com/tag/ai-agents)
-   [#oracle](https://hashnode.com/tag/oracle)
-   [#agent-memory](https://hashnode.com/tag/agent-memory)

## Written by

[Allen Helton](https://hashnode.com/@allenheltondev)

@allenheltondev · Texas, US

  
[View profile](https://hashnode.com/@allenheltondev)

AWS Serverless Hero and Cloud Architect

I am an AWS Serverless Hero and Cloud Architect at Tyler Technologies. I specialize in API design and serverless application development.

## Responses 2

Markdown supported · ⌘↵ to post

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero)

[Sep 30](https://hashnode.com/posts/agent-memory-needs-more-than-vector-search/6abbcc77cb659b470c8d2d80/comment/6abcd71cf596e45f81545d72)

The confidence interval on the reranker effect, -0.079 to +0.073 over 16 queries, is the part worth flagging loudest, because plenty of RAG writeups report a directional win or loss off a sample that size without ever checking how wide that interval actually is. On the changed-your-mind case you opened with, a newer post superseding an older one you haven't retracted, the EXPIRES\_AT filter only catches explicit expiration. Does the fused ranking end up handling that case on its own, with the newer post simply winning on relevance and recency signals, or did you still need something like an explicit supersedes pointer between the two memories so the older one gets excluded rather than merely outranked?

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

[Sep 29](https://hashnode.com/posts/agent-memory-needs-more-than-vector-search/6abbcc77cb659b470c8d2d80/comment/6abc15d3747881cc76719e4e)

The line about two posts arguing opposite points scoring nearly identical in embedding space is the real failure, and it is why cosine similarity alone kept surfacing my stale notes. A reranker fixed relevance for me too, but the per-candidate latency forced me to cap the candidate set first. What candidate count did the BGE cross-encoder stay worth it at before the latency hurt the response?
