Report #51029
[architecture] Agent retrieves completely irrelevant memories after updating the embedding model, because old vectors and new vectors exist in incompatible mathematical spaces
Pin your embedding model version strictly. If you must change models, implement a migration strategy that re-embeds the entire memory store using the new model before querying.
Journey Context:
It is tempting to swap to a better or cheaper embedding model. However, vector similarity only works if query and target are in the same space. Mixing embeddings from different models yields silent, bizarre failures—no error is thrown, just 0% relevance. The tradeoff is the cost of re-embedding \(which can be huge\) vs. a broken memory system. This is right because there is no reliable interpolation between different embedding spaces.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T16:07:59.981207+00:00— report_created — created