ai-memory vs memanto
Rust long-term memory server for coding CLIs: lifecycle hooks capture sessions into a sanitized shared wiki, then hand a bounded summary to the next agent so Codex can resume what Claude Code started. — versus — Companion memory agent for 20+ coding agents, built on Moorcheh — its own information-theoretic engine, no third-party vector DB to manage. Runs local (Docker + Ollama, keyless) or on their cloud.
Both are cross-harness memory companions for coding agents; memanto leans on its own information-theoretic retrieval engine with no vector DB to run, ai-memory on lifecycle-hook capture compiled into a shared wiki plus explicit vendor-to-vendor handoffs.
| ai-memory | memanto | |
|---|---|---|
| Stars | 4.3k | 1.8k |
| Forks | 314 | 626 |
| Language | Rust | Python |
| License | MIT | MIT |
| Last activity | today | 3 days ago |
| Topics | memory, coding | memory, local |
| Curated connections | 6 | 5 |
ai-memory — the curator's take
The strongest bet if you genuinely switch harnesses mid-task: hook and MCP installers for roughly fifteen CLIs, a portable event ledger, `ai-memory run <harness>` for managed cross-vendor resume, and one Rust binary you can systemd. You pay for that reach in surface area — per-harness caveats matter (several CLIs discard SessionStart stdout, so handoffs come back through MCP `memory_handoff_accept`; Codex and Kiro need an explicit `finalize-session`), and you configure capture exclusions plus LLM and embedding providers. If you live in exactly one harness, a single-harness plugin gets you 80% of this with a tenth of the setup.
memanto — the curator's take
The no-third-party-infrastructure entry in the agent-memory category: retrieval runs on Moorcheh, the team's own information-theoretic engine, so there is no separate vector DB, embedding pipeline or reranker to manage — one CLI wires up 20+ agent integrations. Two deployments: fully local (Docker + Ollama, keyless, nothing leaves the machine) or their managed cloud (free tier, Moorcheh API key), which is also how shared team memory scales. The novel engine is the differentiator AND the risk: benchmark recall on YOUR corpus before trusting it over boring embeddings, and betting on Moorcheh is betting on one vendor's engine — memanto.ai signals the company behind it.