| I’m an architect at my company and everyone on my team is now using Claude/Codex agents for their work. Managing context in claude.md/agents.md files is fine but so much of the knowledge required doesn’t fit cleanly in one repo or the other. Plus, much of the team (product, design, support) does not work in repos but still needs a place to share context.
I searched for existing solutions to this but only found products meant for managing deployed AI agent memory for use in AI applications. I wanted something that would help my team share the context that lives in our collective heads. I first tried solving this problem by creating a directory structure with an MCP layer on top of it, but that became a pain to maintain. So I started tinkering with creating a platform for context sharing that works for the whole team. For this to work I wanted to prioritize two things above all else: 1. Easy to store valuable context. If it feels like maintaining docs, no one will use it. 2. Easy to share context with the right people. Access controls, read/write permissions, etc. This turned into memsprout. The build out is not revolutionary by any means but I tried to make it as approachable as possible to use. With memsprout your agent can capture memories and you can decide if and when to share them to your teammates in dedicated spaces with access controls, permissions, etc. nto specific buckets So now I am able to store memories for bits of context I define right from my agent conversation as I work and easily share them with my teammates. Q: Do you guys also see this kind of context sharing as a challenge? How have you solved it in your work? |