[rsafaya]

Great work. As someone who spends many hours a day in Claude Code and dreads the dreaded auto compact moment, the memory problem is genuinely a big point of frustration.

Right now I use a skill on every commit (or when the auto compact warning starts showing up) that forces Claude to update its "memory" . It is a flat markdown file that gets stuffed into conversations, not v smart. Claude forgets things I've told it dozens of times.

Your MCP server approach makes total sense. The create_atom tool alongside semantic_search makes it read/write from day one. I would love to wire a stop hook to automatically atomize session insights (the write side). That's the dream: I work on something in my code, Claude learns why, and that knowledge flows into Atomic without me saying "remember this."

[kenforthewin]

Thanks! Integrating Atomic with tools like claude code is one of the more exciting use cases in my opinion. There are a lot of tools for AI memory out there, but not a ton that allow you to browse, organize, and collaborate directly with the memories.