001
Every session starts from zero
Context dies when the process ends. The next run re-reads the same files and re-asks the same questions.
Memory infrastructure for AI agents
Your agent forgets everything. We fixed that.
Persistent episodic, semantic, and procedural memory over MCP, a REST SDK, or the CLI — recall in under 100ms.
Sub-100ms recall ·Stateless MCP ·Python SDK ·Node SDK ·CLI ·Multi-tenant ·Episodic ·Semantic ·Procedural ·Async extraction ·Sub-100ms recall ·Stateless MCP ·Python SDK ·Node SDK ·CLI ·Multi-tenant ·Episodic ·Semantic ·Procedural ·Async extraction ·
The problem
Agents are brilliant in the moment and amnesiac by default.
002
Context windows blow up
Dumping the repo into the prompt is slow, expensive, and still misses the decision you made last Tuesday.
003
Fixes get forgotten
The same bug is solved twice because the workaround never became a memory the harness could recall.
Introducing Memoria
A hosted memory layer your harness can actually call.
Remember on purpose, or emit harness events and let extraction decide. Recall is scored by similarity, recency, and importance, then truncated to a token budget.
- 01 Harness, SDK, or CLI
- 02 Stateless MCP adapter (optional)
- 03 Memory API (auth, scoring, extraction)
- 04 Postgres + pgvector
session · mcp
$ connected · org_id scoped
✓ remember() semantic 18ms
“prefer pytest over unittest”
✓ recall(“test runner”) 41ms
hit 0.91 · we prefer pytest
▍_
Latency
<100ms
p95 cached recall target
MCP
Stateless
Horizontally scalable adapter
Types
3
Episodic / semantic / procedural
Isolation
100%
Tenant-scoped at query time
cached recall███████░░░░░░░░░░░░░░░░░
uncached vector search█████████████████████░░░
Capabilities
Memory that compounds.
[ 01 ]
Hybrid retrieval
Similarity, recency decay, and importance — then truncated to a token budget.
[ 02 ]
Dedup + consolidation
Near-duplicates reinforce instead of cloning. Sessions merge into one memory.
[ 03 ]
Multi-tenant isolation
org_id is required on every query. Cross-tenant recall is a bug, not a feature.
[ 04 ]
MCP and REST
Harnesses use MCP. Scripts use the Python or Node SDK or the CLI. Same remember / recall / emit contract.
[ 05 ]
Async extraction
Noisy tool calls never hit the queue. Preferences and fixes become memories.
[ 06 ]
Google + API keys
Humans sign in with Google. Machines use mem_… keys hashed at rest.
Works with
OpenCodeClaude CodeCursorLangGraphany MCP clientPython SDKNode SDK
FAQ