memanto vs memsearch
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. — versus — Zilliz's unified memory for coding agents: one Markdown + Milvus store shared across Claude Code, Codex, OpenCode and OpenClaw — hybrid search, plus repeated workflows distilled into skills.
Same job — one persistent memory shared across your coding agents — opposite infrastructure bets: memsearch runs Markdown + Milvus with embedding models you manage; Memanto runs on Moorcheh, its own information-theoretic engine — local Docker (keyless) or managed cloud.
| memanto | memsearch | |
|---|---|---|
| Stars | 1.9k | 2.6k |
| Forks | 647 | 239 |
| Language | Python | Python |
| License | MIT | MIT |
| Last activity | 4 days ago | 4 days ago |
| Topics | memory, local | memory, coding |
| Curated connections | 5 | 8 |
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.
memsearch — the curator's take
The cross-platform play is the point: a conversation in Claude Code becomes searchable context in Codex, OpenCode and OpenClaw — one memory, four plugins, zero per-agent setup. Memories live in readable Markdown (greppable, versionable) with Milvus doing hybrid search, and the standout feature is procedural: it watches for workflows you repeat and distills them into installable skills, maintained in the background. NOT for single-agent loyalists — if you only run Claude Code, opencode-mem-style plugins are lighter — and it's a Zilliz project: the Milvus dependency is also the funnel; check what 'backed by Milvus' costs you operationally before teams adopt.