This is an early release preview. You may encounter bugs.
Memanto logo
Unclaimed

Tool memory

Memanto

a companion agent that manages the memories of your other agents: what to keep, what conflicts, what expires, and who needs to know.

A 82/100 GitHub score ? This grade is derived from GitHub signals, not user votes. Open for the full breakdown.
Discussion

01 / Summary

About Memanto.

Memanto is a memory agent: a companion agent that runs beside your other coding agents and manages their shared long-term memory. Instead of only storing what agents write, it decides what to keep, merges duplicates, resolves contradictions between agents, expires stale memories by policy, and briefs each agent with the relevant slice of memory before it acts.

It observes agent conversations and extracts decisions, preferences, facts, and failures rather than archiving whole transcripts. When new knowledge contradicts old, it supersedes the old memory while keeping a record of what was believed and when, so recall can answer both what is true now and what was believed at a past date or before a release. A scheduled daily run curates new memories, merges duplicates across agents, and flags contradictions for review.

Memories are typed into 13 categories, such as instruction, fact, decision, goal, and preference, and each carries a confidence score, source, provenance, and timestamp. Each agent has its own namespace. A memory is active or expired, expiry comes only from a retention policy you set, and expired memories stay recallable with a label and can be restored.

Recall runs on a bundled semantic engine, either as a local Docker container with Ollama models and no account or as a free cloud service, and memories are searchable as soon as they are written. The whole memory estate exports to the Open Knowledge Format as plain Markdown, and Memanto imports from other memory systems. Python, TypeScript, and Go SDKs, a REST API, a CLI, and a local web dashboard are available.

  • Extraction: pulls durable decisions, preferences, facts, and failures out of agent conversations
  • Consolidation: merges duplicates and fragments into one canonical memory estate shared across agents
  • Conflict reconciliation: supersedes contradicted memories while keeping their history, and surfaces disagreements between agents for review
  • Retention policies: per-type retention and named rules that expire memories, with stamped, reversible expiry
  • Agent briefing: hands each agent the minimal relevant memory before it acts
  • Temporal recall: queries what was believed as of a date or what changed since a release
  • Typed memories: 13 memory categories with confidence, source, provenance, and timestamp on every entry
  • Agent connectors: connects to Claude Code, Codex, Cursor, Windsurf, Gemini CLI, Cline, Continue, OpenCode, Goose, Roo, GitHub Copilot, and others
  • Portable estate: exports to the Open Knowledge Format as Markdown and imports from Mem0, Letta, Supermemory, Zep, and Hindsight
  • Local or cloud backend: a local Docker and Ollama setup with no account, or a free cloud service, switchable without losing memory
  • File ingestion: brings PDF, Word, Excel, JSON, CSV, text, and Markdown files into an agent's namespace
  • Dashboard and summaries: a local web UI over the estate and a daily digest of what changed across agents

02 / Discussion CREDIBILITY-GATED

Discussion

Reading is open to everyone. Posting and voting need a verified identity or a GitHub grade of B or higher.

  • No discussions yet.

04 / Build

Build with Memanto.

Browse the catalog for frameworks, tools, and harnesses, each scored on real GitHub credibility.

Get Memanto →

Browse the catalog