When transitioning to a team brain, you should maintain your personalized AI agent and connect it to a centralized knowledge base rather than replacing it entirely.
Cole Medin, who makes videos about building personal AI knowledge systems, has been describing what happens when the "second brain" approach — one AI assistant that knows your files, your preferences, your history — gets scaled up to a whole team. His answer, which he says is already working rather than theoretical: don't merge everyone into one shared assistant. Keep each person's customized agent, and point all of them at one shared knowledge base.
The distinction he draws is worth unpacking, because "team brain" sounds like it should mean a single AI that everyone talks to. It doesn't. In Medin's framing, the team brain is not an assistant at all:
The team brain is really more just the knowledge base that we access.
The assistant — the thing with a personality, a memory of how you work, instructions tuned to your role — stays personal. What gets centralized is the knowledge: company policies, documentation, shared reference material. As he puts it:
we distribute the policy and the knowledge, but we still maintain the personal agent with the personality and the part of the memory system for that individual.
In plain terms: think of it less like giving everyone the same assistant, and more like giving every assistant access to the same library. Your assistant still remembers that you prefer short answers, that you handle sales and not engineering, that last week you were working on a specific client problem. But when it needs to know the company's refund policy or the spec for a product, it reads from the same source everyone else's assistant reads from.
The honest answer is that this is for people who build or configure AI systems — and that skews technical. Setting up a shared knowledge base that multiple agents can query, wiring a personal agent to it, and deciding which memories stay local versus shared is work for the person running a team's AI tooling, not something a typical employee does over a weekend. If you are a non-developer who simply uses an AI assistant, the useful takeaway is narrower: when your workplace adopts shared AI, you do not have to accept a generic one-size-fits-all bot, and it is reasonable to ask whoever administers it whether your personalized setup can connect to the shared knowledge rather than be replaced by it.
That said, the audience for this pattern is real and growing. Anyone who has spent months tuning an assistant — teaching it their writing style, their projects, their recurring tasks — has something to lose when a company announces a standardized AI rollout. The appeal of Medin's architecture is that shared knowledge and personal memory are not in competition. One lives in the knowledge base; the other lives in the agent.
Medin describes it as something that is shipping, and the underlying pieces — a central document store plus agents that retrieve from it — are well-established techniques, not speculation. Nothing here requires unreleased technology.
What a vendor or an enthusiast would not volunteer: the brief gives no detail on cost, on which tools implement this, or on how hard the setup actually is. It also leaves open the genuinely hard questions — who controls what goes into the shared knowledge base, what happens when company policy and a personal agent's instructions conflict, and how much of an individual's "personal memory" remains private once it operates inside a company system. The idea is clear and the architecture is plausible; the governance is the part nobody has fully answered.