This is the real Locamem ranker running client-side. Type a query, get hits back with a per-facet score breakdown — content similarity, keyword, salience, temporal. Open your network tab: nothing leaves this page. That's the whole product in one widget.
Spins up a local SQLite file and an MCP server. No account, no keys, no signup wall.
Same two-layer model the cloud guys use, with one difference: both layers sit on your disk. Nothing is staged in someone else's database first.
The live transcript: messages, tool calls, intermediate facts. The agent's short-term attention, not its long-term record — nothing leaks into permanent state.
Worth-keeping facts get distilled out of the buffer into one SQLite file you can copy, diff, back up, or rm. Survives restarts, machines, and you.
Cloud products split short-term and long-term across a network boundary; here the boundary is a function call, and both halves stay on the box you can audit.
Every step runs on-device. Drop a packet sniffer on the box and you'll watch nothing leave.
Same product shape. Opposite trust model. Pick local-first when proving zero egress matters more than someone else running the database.
| Locamem (local-first) | Cloud agent memory |
|---|
Locamem ships an MCP server over stdio and streamable-HTTP. Point any MCP client at it and your agent captures and recalls automatically — no SDK, no glue code.
# add Locamem to Claude Code (stdio) claude mcp add locamem -- python -m ha5h.mcp.server --crystal ~/.locamem # or run the HTTP transport for shared / multi-client use python -m ha5h.mcp.server --transport http --port 3100 # -> point any MCP client at http://127.0.0.1:3100/mcp
The agent spawns Locamem as a child process and reads/writes one SQLite file. Nothing binds a port, nothing leaves the box. Works in Claude Code, Claude Desktop, Codex, Cursor, or any MCP client.
Run one server, attach many clients. Bind to 127.0.0.1 so it never accepts a non-local connection.
The memory is a single SQLite file you own. Pick how strictly you want to lock it down. Sync is opt-in, off until you turn it on, and it runs on your hardware.
One file under your home directory. Back it up by copying the file, move it by moving the file, inspect it with any sqlite3 client. No accounts, no keys, no per-recall billing.
Disable the optional embedding-model download and sync; runs with the network cut. Same SimHash + FTS5 ranker, same recall. Built for SCIFs, regulated VPCs, and laptops on planes.
Replicate the crystal across your own machines, point-to-point, no third-party processor in the path. Off by default.
Three places where "prove the data never left" is not a nice-to-have.
Context that can never touch a third-party processor. Read the trail, diff the file, attest to zero egress.
No vendor BAA to negotiate, no egress story to defend. The data boundary is your own machine.
A per-facet score breakdown and a temporal trail that never deletes. Built for reviewers, not black boxes.
No account. No keys. One SQLite file and an MCP server, on your machine.