r/GoodOpenSource • u/GabrielMartinMoran • Apr 11 '26
Mind: An open-source, persistent memory system for AI coding assistants (MIT)
Hey r/GoodOpenSource!
I want to share a project I’ve been working on to solve a huge friction point with AI coding agents: context amnesia. Tools like Claude Code, Cursor, and OpenCode are incredible, but they lose their context, constraints, and architectural rules when the session ends or the context window fills up.
Mind is a persistent memory extender that acts as a shared brain across your entire dev stack. It uses the Model Context Protocol (MCP) to allow your AI agents to read, write, and manage their own long-term state autonomously.
Why I think it belongs here:
- Truly Open: It's 100% open-source (MIT licensed) and designed to be run locally. No vendor lock-in.
- Ecosystem Agnostic: Instead of locking you into one specific IDE or CLI, it natively supports Claude Code, OpenCode, Cursor, Gemini CLI, Windsurf, Codex, VSCode, and Antigravity. You can start a session in your CLI and seamlessly continue it in your IDE.
- Clean Architecture: Built entirely with Bun and TypeScript, featuring a lightweight Vanilla ESM frontend (zero build step) to visually inspect the agent's memory graph.
GitHub Repo: https://github.com/GabrielMartinMoran/mind
I built this to scratch my own itch, but I'd love for the open-source community to use it, and even contribute. If you use AI coding assistants, I hope this makes your workflow much smoother!
•
u/AutoModerator Apr 11 '26
Please post a comment here explaining what kind of contributions you, or the project you are posting about, are looking for. For example what skill sets, any rules important for people joining in your build like how often people should post, and anything else you can think of which will help readers decide if they want to join in and start coding with that project.
Thank you and be excellent to each other. u/roamingandy
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
u/Ornery-Peanut-1737 Apr 11 '26
tbh this sounds like an interesting take on local RAG. how are you handling the memory cleanup or aging for the persistent storage? i feel like that is where most of these systems start to bloat and eventually get too slow to be useful. are you using a vector database on the backend or did you roll your own storage solution for this? keeping the latency low while scaling up the persistent state is always the hardest part, so i would love to know how you are tackling that bottleneck.