I think this is an interesting idea, but I don't see a reason to use it in the current state. Claude Code can already create memories and those work similarly, except Claude "reflects" and "validates" memories only when you tell it that they are wrong.
If you are missing business context, update CLAUDE.md yourself. In a project where Claude makes few mistakes (like a web app) you don't need any form of memory. If it is something complex, it will not help. I work on an anti-detect Chromium fork and tried creating memories for every iteration of changes, recording what worked and what didn't. At some point it just made things worse by Claude confidently doing some nonsense while refernsing test results from a previous Chromium version.
I think this is an interesting idea, but I don't see a reason to use it in the current state. Claude Code can already create memories and those work similarly, except Claude "reflects" and "validates" memories only when you tell it that they are wrong.
If you are missing business context, update CLAUDE.md yourself. In a project where Claude makes few mistakes (like a web app) you don't need any form of memory. If it is something complex, it will not help. I work on an anti-detect Chromium fork and tried creating memories for every iteration of changes, recording what worked and what didn't. At some point it just made things worse by Claude confidently doing some nonsense while refernsing test results from a previous Chromium version.