You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> A fact written into `memory/YYYY-MM-DD.md` is visible in startup context, but `memory_recall`**will not find it** unless it was also written via `memory_store` (or auto-captured by the plugin).
136
+
137
+
**What this means for you:**
138
+
- Need semantic recall? → Use `memory_store` or let auto-capture do it
139
+
-`memory/YYYY-MM-DD.md` → treat as a **daily journal / log**, not a recall source
140
+
-`MEMORY.md` → curated human-readable reference, not a recall source
141
+
- Plugin memory → **primary recall source** for `memory_recall` and auto-recall
142
+
143
+
**If you want your Markdown memories to be recallable**, use the import command:
144
+
```bash
145
+
npx memory-lancedb-pro memory-pro import-markdown
146
+
```
147
+
132
148
Validate & restart:
133
149
134
150
```bash
@@ -620,19 +636,6 @@ Sometimes the model may echo the injected `<relevant-memories>` block.
Auto-recall has a configurable timeout (default 5s) to prevent stalling agent startup. If you're behind a proxy or using a high-latency embedding API, increase it:
If auto-recall consistently times out, check your embedding API latency first. The timeout only affects the automatic injection path — manual `memory_recall` tool calls are not affected.
0 commit comments