Durable graph and vector memory for AI agents
Store graph relationships, embeddings, compressed context, and provenance in one local binary. Connect through 19 prime_* memory tools or the HTTP API; optional inbox and hound modules bring the full Prime registry to 27 tools.
Connect Prime to Claude Desktop
Add to ~/.claude/claude_desktop_config.json:
{
"mcpServers": {
"prime": {
"command": "allsource-prime",
"args": ["--data-dir", "~/.prime/memory"]
}
}
}19 prime_* memory tools cover graph CRUD, vector search, hybrid recall, compressed index, and temporal queries.
How it works
How does an agent remember?
Every accepted fact becomes an immutable event in AllSource Core. The WAL and Parquet files persist the event history; Prime derives graph nodes, vectors, and relationships from it for recall.
- Graph nodes: entities, concepts, decisions
- Vector embeddings: semantic similarity search
- Compressed index: navigational scaffolding
How fast is recall?
The published Core reference benchmark measured 11.9μs p99 projection reads. Prime hybrid recall adds vector similarity, graph traversal, and temporal recency, so end-to-end recall depends on query and hardware.
- Vector search: HNSW index over embeddings
- Graph expansion: 1-hop BFS from matches
- Compressed index: cross-domain reasoning
What about cross-domain questions?
Prime's compressed index adds domain summaries and cross-references to graph and vector retrieval. A published AllSource project benchmark measured its effect on one cross-domain evaluation; results depend on your corpus and queries.
- Auto-generated from graph events
- Organized by domain with cross-references
- Evaluation method and corpus are published
Can I time-travel?
Every mutation is an append-only event. Query any entity's state at any past timestamp. See who added what, when, and why.
- as_of queries: reconstruct past state
- Full audit trail: every create, update, delete
- Graph diff: what changed between two timestamps
Cross-domain result: see the published project benchmark and method.
Choose the layer you need
Core is the durable record. Prime adds retrieval. Hosted removes infrastructure work.
AllSource Core
Durable ordered event history, replay, point-in-time reconstruction, and provenance.
See detailsAllSource Prime
Graph, vector, compressed-index, and temporal recall derived from Core events.
See detailsAllSource hosted
Managed Core access with retention, event, stream, and MCP limits set by plan.
See detailsNot every app needs event-sourced memory. Use simpler current-state storage when replay, provenance, and historical reconstruction do not affect your product or operations.
Use cases
Personal AI Assistant
Claude remembers your project context across sessions. Yesterday's decisions inform today's answers.
Multi-Agent Knowledge Sharing
Three agents work on different parts of a codebase. Findings flow through the shared graph.
Incident Response Memory
Your oncall agent remembers every past incident. 'What happened last time this alert fired?'
Research Assistant
Read 50 papers, build a knowledge graph. The compressed index surfaces unexpected cross-domain connections.
Code Review Context
Agent remembers past review feedback. 'Last time you said X about error handling in this module.'
Audit & Compliance
Full provenance on every memory. Who added what, when, from what source. Time-travel to any past state.
One engine, not three databases
┌─────────────────────────────────────────────┐ │ AllSource Prime │ │ │ │ Graph Vectors Temporal Compressed │ │ Nodes HNSW History Index │ │ Edges Embed Time-travel Cross-refs │ │ Similar Diff │ │ │ │ ┌──────────────────────────────────────┐ │ │ │ AllSource Core Engine │ │ │ │ WAL + Parquet + DashMap + HLC + CRDT │ │ │ │ 469K events/sec │ 11.9μs p99 reads │ │ │ └──────────────────────────────────────┘ │ └─────────────────────────────────────────────┘
Prime records vectors, graph nodes, and edges as events in Core, then derives queryable memory views from the same durable history.
Install Prime locally
One command. No cloud account. No API key.