From 3133f54682881eae6b53480a85263ba1150b0853 Mon Sep 17 00:00:00 2001
From: Aditya kumar singh <143548997+Adityakk9031@users.noreply.github.com>
Date: Thu, 27 Aug 2026 22:26:47 +0530
Subject: [PATCH] docs: document self-hosted v0.0.5 model mixing bug and v0.0.7
 resolution (#1450)

---
 apps/docs/self-hosting/embeddings.mdx | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/apps/docs/self-hosting/embeddings.mdx b/apps/docs/self-hosting/embeddings.mdx
index ce6d41c52..7f0f62573 100644
--- a/apps/docs/self-hosting/embeddings.mdx
+++ b/apps/docs/self-hosting/embeddings.mdx
@@ -129,6 +129,14 @@ Use the dimension published for your chosen model. A mismatch with vectors alrea
 
 **Changing embeddings later:** Not supported in place. Start from a fresh data directory or re-ingest all content so vectors stay comparable.
 
+> [!IMPORTANT]
+> **Model Mixing Bug in v0.0.5 (Exact match returns nothing)**
+>
+> In version `v0.0.5`, there was a bug where the server could mix different embedding models between write and read paths (e.g., document ingestion using OpenAI but memory queries using local default embeddings). In multilingual contexts like Japanese (which lacks space tokenization for fallback lexical FTS matching), this caused exact-text memory searches through `/v4/search` and `/v4/profile` to silently return `{"results":[],"total":0}`.
+>
+> **Resolution:**
+> This was fully resolved in `v0.0.7` by locking the embedding plan uniformly across all document and query embedding paths (enforced via a locked plan in the database store). If you are running `v0.0.5` and experiencing this issue, you should upgrade to `v0.0.7` or later.
+
 ## Related
 
 - [Configuration](/self-hosting/configuration) — LLM providers, storage, ingestion limits