About MemorySQL
MemorySQL captures AI agent sessions (Codex, ZCode, Claude Code, Gemini, Cursor, OpenCode, Hermes), stores persona and long-term memories, and serves everything over a local MCP server so any agent can pick up exactly where the last one left off.
Full-text plus local semantic search (sqlite-vec + bge-small-zh, fully offline), project handoff briefs, structured end-of-work progress reports and auto-generated project devlogs. There is no telemetry and no analytics of any kind.
Privacy-relevant behaviour is documented in full in the disclosure linked below:
- Agent conversations, memories, notes, project instructions and configuration-derived content are stored in PLAINTEXT on your machine. Use full-disk encryption if that matters for your setup.
- If you configure an OpenAI, Anthropic or local Ollama provider, EXCERPTS of your conversations and memories are sent to that provider, with API keys, private keys and email addresses redacted first. Leave the provider unset to stay fully local.
- Exporting to a folder writes COMPLETE PLAINTEXT messages and memories into the folder you choose. If that folder is inside OneDrive, Dropbox or a similar service, those files are replicated by that service.
- The resident MCP endpoint exposes raw stored content over UNAUTHENTICATED localhost HTTP, bound to 127.0.0.1. It is deliberately unauthenticated so local agents can connect. Any process running on your machine can read your entire knowledge base. See the disclosure for the local-origin protections and the trust assumptions involved.
