Problem
The dashboard Memories search cannot look up a memory by its ID.
Repro
- Open dashboard, select a project (e.g. with 1700+ memories).
- Go to the Memories tab.
- Type a memory number, e.g.
1451 or #1451.
Expected: exact hit #1451.
Actual: no hit for #1451 -- instead an unrelated memory (e.g. #1526) is returned. Searching #1451 behaves the same.
Why it matters
Agents routinely cite memories as (#831), (#863), etc. (e.g. operator-gated next steps referencing a memory ID). There is currently no way to resolve such a reference in the dashboard -- the only path is ctx_memory get <id> from a session in the same project, or raw SQLite (WHERE id = N).
Evidence
- The returned hit carries an
embedded badge, i.e. the numeric query goes through semantic/full-text ranking instead of an ID equality match.
- Repo-side research: only documented behavior is semantic auto-search (
score_threshold: 0.6, local embeddings); no ID filter is documented anywhere.
Suggestion
If the query matches an ID pattern (optional # followed by digits), resolve it as an exact ID lookup first (scoped to the selected project), and only fall back to full-text/semantic ranking when there is no such ID. Alternatively add an explicit ID filter next to the status/category dropdowns.
Env
- Windows app (Magic Context dashboard), Memories tab with status/category filters
- magic-context plugin 0.44.4 (global,
@cortexkit/opencode-magic-context)
Problem
The dashboard Memories search cannot look up a memory by its ID.
Repro
1451or#1451.Expected: exact hit
#1451.Actual: no hit for
#1451-- instead an unrelated memory (e.g.#1526) is returned. Searching#1451behaves the same.Why it matters
Agents routinely cite memories as
(#831),(#863), etc. (e.g. operator-gated next steps referencing a memory ID). There is currently no way to resolve such a reference in the dashboard -- the only path isctx_memory get <id>from a session in the same project, or raw SQLite (WHERE id = N).Evidence
embeddedbadge, i.e. the numeric query goes through semantic/full-text ranking instead of an ID equality match.score_threshold: 0.6, local embeddings); no ID filter is documented anywhere.Suggestion
If the query matches an ID pattern (optional
#followed by digits), resolve it as an exact ID lookup first (scoped to the selected project), and only fall back to full-text/semantic ranking when there is no such ID. Alternatively add an explicit ID filter next to the status/category dropdowns.Env
@cortexkit/opencode-magic-context)