Google PM open-sources Always On Memory Agent, ditching vector databases(venturebeat.com)
venturebeat.com
Google PM open-sources Always On Memory Agent, ditching vector databases
https://venturebeat.com/orchestration/google-pm-open-sources-always-on-memory-agent-ditching-vector-databases-for
6 comments
Been saying this for a while. Vector similarity is the wrong primitive for agent memory. It finds things that sound related, not things that are actually relevant given current context and what the agent already knows.
The "ditching vector databases" framing is a bit dramatic since you still need embeddings somewhere, but the point stands that a raw vector store with no resolution layer is basically a pile of notes your agent can't reason about. You need conflict detection, certainty weighting, temporal scoping. Otherwise you're just building a fancier version of the same problem
The "ditching vector databases" framing is a bit dramatic since you still need embeddings somewhere, but the point stands that a raw vector store with no resolution layer is basically a pile of notes your agent can't reason about. You need conflict detection, certainty weighting, temporal scoping. Otherwise you're just building a fancier version of the same problem
I wonder if this is Google's answer to Beads?
Google's own ADK framework already has memory. Whatever VB is posting is far less interesting. But they need to sell that attention too I guess
[deleted]
Your vector database should be in memory
https://github.com/LabLeaks/spotless