0d3sa Memory
Local-first memory for coding agents
Semantic recall, knowledge packets, and dreaming — in one SQLite file on your machine. Optional encrypted sync via self-hosted relay.
Install in moments
Install the binary, wire your project, optionally add a skill, then store your first memory.
- 1. Install memory
curl -fsSL https://0d3sa.com/memory/install.sh | shOne static binary: memory, sync, and the MCP server. Verifies the checksum, installs to
~/.local/bin. - 2. Wire your project
cd ~/my-project && od3sa-memory setup claudePrompts for an agent identity and personal-vs-team scope, then writes a project-local env file and the MCP config.
- 3. Install a skill for your agent optional
Skills add ready-made prompts and rules for your client. Grab one from the skills registry — Claude Code, Cursor, Hermes, or any MCP client.
- 4. Launch your agent
Open the project in your MCP client — restart it first if it was already running — so the MCP server loads. In Claude Code, confirm with
/mcp. - 5. Verify setup
od3sa-memory healthThen ask your agent to remember something — or follow the quick start.
Pick the surface that matches what you are building today.
od3sa-memory
Local-first SQLite memory with vector embeddings, an MCP server, knowledge packets, dreaming, and encrypted multi-device sync. Streamable HTTP MCP is available for self-hosted operators (v0.7.0+) — run od3sa-memory with --http on your machine or VPS. This is not a hosted MCP gateway.
od3sa-relay
A lightweight, single-binary sync relay for always-on hosts. Opaque to the operator: it stores directory data and encrypted envelopes, nothing else.
Prebuilt skills for your agent.
Claude Code CLI
Slash commands and rules that make Claude Code use memory as its persistent memory layer.
View skill →Cursor
Agent rules for wiring memory into Cursor as a persistent skill.
View skill →Hermes Agent
Skill file that gives the Hermes agent persistent recall across sessions.
View skill →Any MCP client
Tool-usage guidance for any stdio MCP client — the base skill the others build on.
View skill →Every release ships two static Go binaries.
- od3sa-memory~66–107 MB
Memory, MCP server, sync, and device pairing
- od3sa-relay~10–11 MB
Self-hosted relay for encrypted multi-device sync
Which one do I need?
I want memory in Claude Code
Install memory, then run od3sa-memory setup claude in the project directory.
I use another MCP client
memory speaks stdio MCP. See connecting other MCP clients.
I need multi-device sync
Follow syncing two devices through a relay. Contents are encrypted end-to-end.
I want to run my own relay
Deploy the relay binary on any always-on host — or on a public VPS.