Continuity for agents
Recall project decisions and constraints across supported coding tools instead of rebuilding context at every session.
Hyphae Local data and agent memory
One local home for data and useful memory.
Hyphae combines SQL, native structures, lexical and vector search, transactions, and recovery in one Rust engine. Agent Memory turns that foundation into shared context for coding agents.
Keep useful context across sessions while retaining control of the data and its record.
01 / Why it matters
Why this work matters
A shared data foundation
Relational data, structures, and search share the same durable storage and transaction authority.
Local ownership
Run embedded or through local clients, with no required cloud account or external database.
Inspectable state
Retain backups, recovery records, and proofs that can be checked against the documented snapshot.
02 / How it works
How it works
The main stages make the project’s boundaries visible.
- 01
Applications and agents
CLI, embedded Rust, typed clients, local protocol, and the memory MCP profile
- 02
Local data engine
SQL, native structures, and lexical/vector search share transaction boundaries
- 03
Durable record
Write-ahead log, snapshots, lifecycle state, checkpoints, and recovery
- 04
Recall and verification
Project-scoped context with optional proof material and offline verification
03 / Capabilities
Current capabilities
Agent Memory
Store, recall, forget, and separate personal, work, and journal context with project boundaries and expiry.
SQL and keyspace
Versioned, bounded queries and native data structures, expanded in the 3.0.0 release.
Search
Lexical, exact-vector, approximate, filtered, and hybrid retrieval within the shared engine.
Operations
Embedded or local multi-client use, optional HTTP, typed clients, backup, restore, and diagnostics.
04 / Evidence
Evidence and its scope
The release has public package receipts, a dedicated-hardware report, and an abstract commit-protocol model.
published Native release
commit-protocol model
dedicated-hardware report
Hardware observations apply to the named workloads and source. The formal model is not a proof of the implementation; recall proofs do not establish the truth of remembered text.
What it does now
- Ships a unified local engine and Agent Memory in the stable release.
- Supports project-scoped recall and memory lifecycle operations.
- Provides source-bound release archives, package identities, and verification material.
Next directions
- Evaluate retrieval quality under reproducible, publicly inspectable protocols.
- Develop richer memory integrations while identifying their required source versions.
- Expand supported workloads through measured correctness and performance gates.
Limits to keep in view
- The Omarchy memory-panel interface requires source work after 3.0.0; it is not in the published 3.0.0 packages.
- The 3.0.0 memory MCP does not expose every vector capability of the underlying engine.
- A single local service owns the data directory; distributed operation is a separate scope.
- Stored statements can be wrong. Proofs establish documented records and retrieval, not factual truth.
Hyphae