mat10112

Agreed. We started out with that actually at my company. I created a repo that defined our systems taxonomy, how things relate to each other, glossary of terms, etc. Then created an internal MCP to sit in front of it for everyone's agents to use. It did very well initially but eventually became a pretty big burden to maintain especially for the non-technical team members that are not used to the git process for making updates. I wanted to create something that allowed the rest of the non-technical folks to easily contribute to our teams source of truth. Now in memsprout they have their own spaces they create and own so they can manage when, what, and with whom their context is shared.

Also want to acknowledge this approach has some limitations. Human judgement in sharing and managing context is still crucial. What I think memsprout does is provide transparency in shared context management. But the last mile is still (and should still imo) be human owned.

And I thought of a concrete example as a use case: acronyms, code names, etc. Every company I have been at has tons of these. In my first attempt of a repo based approach we used an .md file as a “glossary” of company terminology. But updating that file became a tedious, focus shifting, task. With memsprout as soon as I explain to claude that “StepLadder” is our new product line, claude can store that as a memory and immediately make that new insight available to the rest of my team’s agents.