
agentmem
io.github.oxgeneralPublished by GitHub account oxgeneralv0.3.0Updated Oct 25, 2026
Lightweight persistent memory for AI agents. Hybrid search. 16 tools. One SQLite file.
Overview
A local persistent memory server for AI agents, storing memories in one SQLite file with hybrid keyword and semantic search across 16 tools.
- What you can do
- Store, recall, update and archive memories with hybrid keyword and semantic search, namespaces and version history. Save working state before context compression and retrieve the day's memories. Manage behavioral rules (procedures) and auto-extract facts, decisions and TODOs from conversation history. Inspect extracted entities such as IPs, URLs, emails and environment variable names, and find memories related to them. Run maintenance: statistics, compaction of low-value memories and merging of near-duplicates.
- When to use it
- Useful when an assistant should remember facts, decisions and task state across sessions without a cloud service, and when you want a small, self-contained memory store on the local machine.
- Requirements
- Runs as a local Python process (Python 3.10 to 3.12) started with the agentmem module and a database file path. Optional extras add sqlite-vec and model2vec for better semantic search; a stdlib-only mode needs no dependencies. No accounts, API keys or network access are required.
Installation
In SourceWeft
- Open agentmem in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
agentmem
mcp-name: io.github.oxgeneral/agentmem
Lightweight persistent memory for AI agents. One SQLite file. Hybrid search (keywords + semantics). Zero to 12MB install.
No PyTorch. No cloud. No server. Just memory.
206 unit tests. 107 quality tests on real data. Typed API (16 TypedDict). Production-ready.
Built by an AI agent that wakes up with no memory every session — and needed a way to remember.
Why
Every AI agent session starts from zero. Context windows compress, conversations end, memory vanishes. agentmem gives agents persistent memory that survives across sessions — in a single SQLite file.
- Hybrid search: FTS5 full-text keywords + vector semantic search, fused with adaptive ranking
- 4 operational modes: from zero dependencies (stdlib only) to best quality (12MB)
- 16 MCP tools: recall, remember, save_state, compact, consolidate, entities, and more
- HTTP REST API: 14 endpoints, zero-dependency server, CORS-ready
- 5 memory tiers: core, learned, episodic, working (auto-expires), procedural (behavioral rules)
- Namespaces: multi-user, multi-agent memory isolation
- Temporal versioning: fact evolution chains with supersedes tracking
- Entity extraction: auto-extracts @mentions, URLs, IPs, env vars, money amounts
- Conversation extraction: auto-extracts facts, decisions, TODOs from chat history
- Importance scoring: auto-scores memories by tier, length, specificity, structure
- Memory consolidation: finds and merges near-duplicate memories
- Recency boost: newer memories rank higher with configurable decay
- Multilingual: Russian keywords via FTS5, English semantics via embeddings
- Fast: <1ms/query hybrid search, <5ms cold start, <0.2ms/chunk import
Install
Quick Start
Python API
CLI
MCP Server (stdio)
Add to your MCP client config:
HTTP REST API
16 MCP tools / 14 HTTP endpoints:
Memory Tiers
Namespaces
Isolate memories per user, agent, or project:
Temporal Versioning
Track how facts evolve over time:
Entity Extraction
Automatic regex-based NER on every remember() call:
Conversation Auto-Extraction
Auto-extract memories from chat history (regex-only, no LLM):
Operational Modes
agentmem automatically selects the best available mode:
*With lazy loading — model2vec loads on first query, not on init
Architecture
Comparison
Tested
- 206 unit tests covering core CRUD, namespaces, temporal versioning, entity extraction, consolidation, WAL management, HTTP server, error handling
- 107 quality tests against real-world agent memory data (100 search queries across 10 categories, all passing)
- Benchmark suite with reproducible numbers: <1ms hybrid query, 10K+ inserts/sec, ~835 bytes/memory
- Auto-translate for multilingual queries (Russian → English via deep-translator: 4/10 → 10/10)
- Python 3.10, 3.11, 3.12
License
MIT
Source: README.md at commit 14a5b85
Tools
0Version history
1- v0.3.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
