Second Brain for Teams is live today
Running four AI tools means four tools that each know a different half of what you told them. On a team it gets worse, because the half your colleague explained on Tuesday never reaches you at all.
I have been building Second Brain around that problem for a while. Today the team version went live: every member gets a private layer, the team gets a shared one, and recall reads across both. It runs in your own Cloudflare account and it is still MIT.
What I actually want to hear about is the smaller version of the problem. If you work with other people and you have Claude or Cursor open all day, what is the one piece of context you are tired of typing out again? The vendor you already ruled out. The reason the schema looks the way it does. The customer request everyone remembers slightly differently.
I will be here all day and I will answer anything about how it works underneath.
Launch: producthunt.com/products/second-brain-cloudflare?launch=second-brain-for-teams-2
Replies
All the best team )
@rahilpirani I have to admit this is a problem I've faced more often than I'd care to say. It's really frustrating when the context gets lost between different tools
Second Brain for AI
@charli_decouze1 couldn’t agree more! Hope this works for you! It’s been a lifesaver for me!
@rahilpirani The private and shared memory idea makes sense for teams. How do you decide what the AI should keep private and what should be shared? I feel like that could get messy pretty quickly.
Second Brain for AI
@vincent__fisher it defaults to private unless you have instructed the AI at the start of a session to save to team memory. Additionally, there is also a team setting that will allow you to set your default memory workspace… team or personal.