dsh-plugin-semantic-memory

LIMITATIONS

Known limitations

- **Recall is best-effort and async** — the user-message listener embeds in the background; on a cold start (model still downloading) or with a slow API the first recall may arrive one step late, and the strength-ranked fallback covers that turn. Recall caches are per-session and stale after 60 s. - **Sync prompt injection** — the injected section renders from resident data only; the store is loaded lazily on first tool call, so a brand-new process may start with an empty injection for the first assembly. - **No embedding persistence cache** — vectors are stored inside each entry, so no separate index file is needed, but full re-embedding never happens either (entries keep their vectors forever). - **Brute-force search** — O(n) cosine over all entries per query; fine for personal-scale stores (thousands), not for millions of entries.