Statewave is an open-source, self-hosted memory runtime for AI agents, with a governance layer most tools ignore. Right now, memory in agents is a black box: - no auditability - no control over what s stored - no way to debug why an agent remembers something Statewave tries to fix that. You can run it locally in ~2 minutes: npx @statewavedev/statewave It plugs into Claude Code, Cursor, VS Code Copilot and other MCP clients. No account. Works offline. I ll be around in the comments on launch day, curious what feels broken, over-engineered, or unnecessary.
We're getting ready to launch here, and I'd rather use this thread properly than just show up on launch day.
Short version: Statewave is an open-source memory runtime for AI agents. Self-hosted, Apache 2.0.
The problem we kept running into: agent memory is usually just a vector store. It hands back text ranked by similarity, and that's it. The moment an agent sits in front of real users, someone asks: where did that come from? Who was allowed to see it? Has it been changed? A similarity score answers none of those.
So we treat memory as infrastructure instead. Access policies, sensitivity labels, tamper-evident audit receipts, and provenance on every memory back to the episode that produced it.
