From magnum-memory
Search your magnum-memory history (Checkpoint Log + Archive) for past entries.
How this command is triggered — by the user, by Claude, or both
Slash command
/magnum-memory:recallThe summary Claude sees in its command listing — used to decide when to auto-load this command
Search this project's magnum-memory history for: $ARGUMENTS
1. Run: `"${CLAUDE_PLUGIN_ROOT}/scripts/mm-recall" $ARGUMENTS`
2. It prints whole matching Checkpoint Log / Archive entries — every query word must
appear (case-insensitive, matched per word — not as a phrase), most-recent
(Checkpoint Log) first, then Archive.
3. Present the returned entries concisely and, if useful, summarize what they mean for
the current task. If it prints `no matching entries`, say so and suggest broader terms.Search this project's magnum-memory history for: $ARGUMENTS
"${CLAUDE_PLUGIN_ROOT}/scripts/mm-recall" $ARGUMENTSno matching entries, say so and suggest broader terms.npx claudepluginhub kashifmanzer/magnum-memory --plugin magnum-memory/recallRecalls memories from past Claude Code sessions via the memoir system. Queries by argument with optional --include-metrics flag for telemetry data.
/recallSearches CortexDB global brain for memories and knowledge relevant to the query, expands it with keywords and aliases, and summarizes findings with source IDs.
/recallSearches Honeycomb's memory for prior context matching a query, retrieves relevant hits, and presents summaries with drill-down capability.
/recallRetrieves a memory by exact key, partial key match, or fuzzy value search across project and global stores. Logs access and updates memory vitality tracking with confidence scoring and decay.
/recallSearches Pensyve memory by semantic similarity and text matching, returning ranked results from episodic, semantic, and procedural memory groups.
/recallSearches session history logs by concept keyword, returning matching sessions with relevant bullets and decisions. Results sorted newest-first with deduplication.