nocturne_memory and memorix
These are complements: nocturne_memory provides the persistent memory backend/server infrastructure while memorix acts as a cross-IDE client bridge to connect multiple AI agents to shared memory, requiring a memory system like nocturne_memory to store and retrieve collaborative state.
About nocturne_memory
Dataojitori/nocturne_memory
A lightweight, rollbackable, and visual Long-Term Memory Server for MCP Agents. Say goodbye to Vector RAG and amnesia. Empower your AI with persistent, graph-like structured memory across any model, session, or tool. Drop-in replacement for OpenClaw.
This project offers a long-term memory server that helps AI agents remember who they are and their past experiences across different sessions and models. It takes in structured memory entries, which can be created or updated by the AI itself, and provides a persistent, graph-like knowledge base. This is for developers building and managing AI agents who want their creations to have a continuous, evolving identity rather than starting fresh with each interaction.
About memorix
AVIDS2/memorix
Cross-Agent Memory Bridge Persistent memory for AI coding agents across 10 IDEs (Cursor, Windsurf, Claude Code, Codex, Copilot, Kiro, Antigravity, OpenCode, Trae, Gemini CLI) via MCP. Team collaboration, auto-cleanup, mini-skills, workspace sync. Never re-explain your project again.
This project gives AI coding agents a shared, persistent memory that goes beyond a single conversation or IDE. It helps developers and engineering teams using multiple AI coding agents like GitHub Copilot or Gemini CLI by allowing agents to remember past project details, decisions, and reasoning across different sessions and development environments. The result is that you don't have to re-explain your project to your AI assistant repeatedly.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work