Mem0 Pi Agent Plugin v0.1.2 fixes silent commands and weak memory search
The `v0.1.2` release of the Mem0 Pi Agent Plugin fixes invisible command feedback and adds relevance-filtered memory search with a configurable similarity threshold.
Score breakdown
The release closes a gap where silent notifications and an unfiltered similarity search caused users to miss command results and `/mem0-forget` to surface unrelated memories for deletion.
- 01Commands `/mem0-remember`, `/mem0-forget`, `/mem0-pin`, and `/mem0-scope` now use `pi.sendMessage({ display: true })` for persistent output instead of silent `"info"` notifications.
- 02A configurable similarity `threshold` (`searchThreshold`, default `0.3`) is now passed to the mem0 search API by `/mem0-search`, `/mem0-forget`, and `/mem0-pin`.
- 03Without a threshold, mem0 returned the closest weak memory even for unrelated queries; `/mem0-forget` would then offer irrelevant memories for deletion.
The `v0.1.2` release of the Mem0 Pi Agent Plugin fixes two bugs and improves feedback quality across all commands. The first fix addresses a UX problem where the Pi TUI rendered `"info"` notifications as dim, collapsible status text that overwrote the previous line, making command results easy to miss. The four commands `/mem0-remember`, `/mem0-forget`, `/mem0-pin`, and `/mem0-scope` now use `pi.sendMessage({ display: true })` to produce persistent message blocks, while warnings and errors continue to use `ctx.ui.notify` for prominent display.
This ensures queries with no sufficiently similar memory report no match, and genuine matches are reranked by deeper relevance.
The second fix targets relevance-filtered search. Previously, the mem0 search API ranked results by similarity with no relevance floor, meaning a query with no closely matching memories would still return the nearest (weak) result — and `/mem0-forget` would offer those weak matches for deletion. The `/mem0-search`, `/mem0-forget`, and `/mem0-pin` commands now pass a `threshold` (named `searchThreshold`, defaulting to `0.3` and configurable in `mem0-config.json`), `top_k`, and `rerank` parameters to the API, matching the behavior of the Claude Code and OpenClaw integrations. This ensures queries with no sufficiently similar memory report no match, and genuine matches are reranked by deeper relevance.
On the improvement side, every command now surfaces richer contextual feedback: `/mem0-remember` echoes the stored text and its scope; `/mem0-search` prepends an `N matches for "<query>"` header; `/mem0-forget` and `/mem0-pin` name the query when nothing matches and label disambiguation dialogs with match counts; and `/mem0-scope` explains where new memories will be saved. The `/mem0-dream` consolidation command is also cleaner — the protocol is now sent to the agent hidden (`display: false`) behind a concise "Dreaming…" status line, rather than dumping raw protocol text into the transcript.
Key facts
- 01Commands `/mem0-remember`, `/mem0-forget`, `/mem0-pin`, and `/mem0-scope` now use `pi.sendMessage({ display: true })` for persistent output instead of silent `"info"` notifications.
- 02A configurable similarity `threshold` (`searchThreshold`, default `0.3`) is now passed to the mem0 search API by `/mem0-search`, `/mem0-forget`, and `/mem0-pin`.
- 03Without a threshold, mem0 returned the closest weak memory even for unrelated queries; `/mem0-forget` would then offer irrelevant memories for deletion.
- 04The `searchThreshold` value is configurable in `mem0-config.json` and visible in `/mem0-status`.
- 05Search behavior now matches the Claude Code and OpenClaw integrations by also passing `top_k` and `rerank` parameters.
- 06The `/mem0-dream` consolidation protocol is now hidden from the transcript (`display: false`) behind a concise "Dreaming…" status line.
Topics
Summary and scoring are generated automatically from the original article. We always link back to the publisher and never republish images or paywalled content. Last processed Jun 13, 2026 · 08:58 UTC. How this works →