HYPHAE / LOCAL DATA & AGENT MEMORY
Data stays local.Context stays useful.
SQL, native structures, search, and agent memory. One Rust engine, with a durable record you can inspect.
Stable 3.0.0 · Rust · Apache-2.0 · Published September 4, 2026
01 / CONTINUITY
Start with what the project already knows.
An agent session ends. The decisions do not have to disappear with it.
Agent Memory turns Hyphae’s storage and retrieval foundation into shared context for supported coding tools. Keep control of the data and inspect the record that a recall returns.
The project keeps its data local.
Decision / Project context- 01
Save
A decision becomes useful context.
- 02
Recall
The next session starts with a record.
- 03
Verify
Inspect where the recalled record came from.
02 / ONE ENGINE
Different ways to ask. One durable foundation.
Agent Memory
Store, recall, and forget useful context with project boundaries, expiry, and separate personal, work, and journal layers.
SQL and native structures
Relational queries and a native keyspace share transaction boundaries and one durable storage authority.
Search in the same engine
Lexical, vector, approximate, filtered, and hybrid retrieval operate within the unified engine’s documented contracts.
Operations you can inspect
Embedded use, local clients, backups, recovery, and proof material keep the state and its history accessible.
03 / THE RECORD
Go to the source.
04 / CLEAR BOUNDARIES
A record can be verified. A claim still needs evidence.
Proofs establish the documented record and retrieval. They do not prove that every stored statement is true.
The published 3.0.0 MCP memory surface does not expose every vector capability of the underlying engine. A local service owns the data directory; distributed operation is a separate scope.
Benchmarks apply to their named workloads, hardware, and source revision. The abstract commit-protocol model is evidence about the model, not a proof of the implementation.
CELIUMS / THE WORK CONTINUES