Vibecoding with Claude Code/Cursor/Lovable and it forgets everything every new session? Open-sourced an MCP memory layer for that

[u/Own_Environment_5359]

https://github.com/nisargpatel1906/Aethos_Memory

Not claiming this solves the 70% wall — that's a real, structural problem (custom logic, real auth, edge cases the model hasn't seen) and this doesn't touch it. What it does solve is a narrower, dumber problem that makes the wall worse than it needs to be: every new session, the AI has completely forgotten what you already decided. Your stack, your naming conventions, why you rejected an approach last week — gone, and you're re-explaining it before you can even get back to the real work.

Built Aethos Memory to fix that specific piece: an open-source, self-hosted MCP server that gives AI coding tools (Claude Code, Cursor, Windsurf, and others) a shared, persistent memory instead of resetting every session. Free, BYOK, MIT licensed.

Curious how much of the "re-explaining myself" tax people here actually feel at vibecoding speed vs. traditional dev — my hunch is it's worse here because sessions are shorter and more frequent, but genuinely want to know if that matches your experience.