cagangedik

7 ms·

1. 1.▲
   by cagangedik 6mo ago

   Thanks! The problem isn’t AI chat, it’s tracking what the AI actually does to files. Since we rely on MCP, starting with environments like GitHub and IDEs makes this tractable. If we can own more of that surface (i.e. build our own tool), e
2. 2.▲
   by cagangedik 6mo ago

   Thanks! You hit the nail on the head with the core approach. But to answer your first question: you can't 100% guarantee the AI will call the MCP. That's exactly why we don't rely on it alone. If the AI skips context, our fai
3. 3.▲
   by cagangedik 6mo ago

   Thanks!
4. 4.▲
   by cagangedik 6mo ago

   Thanks!
5. 5.▲
   by cagangedik 6mo ago

   Thanks! claude-mem captures what the AI did locally and replays it next session, great for solo continuity. Hopsule works at the organizational level: shared memories, structured decisions with lifecycle and enforcement, synced across your
6. 6.▲
   Show HN: Hopsule – Persistent memory and decision layer for AI development

   9 points by cagangedik 6mo ago|10 comments