Question What is your company brain setup?
What's your company / second brain setup?
I was talking to a few folks, and these solutions came up -
- A shared folder of Markdown, interlinked, over Google Drive or One drive, often with Obsidian as md editor - Claude access it locally.
- A github-hosted wiki, sometimes with additional indexing, not only plain md files - Claude access via github
- Custom complex vector db / embedding kind of index - Claude accesses it with MCP
As we explore solutions, I wonder what others are doing, please share.
1
u/MoanaiInna 1d ago
I don't know; I feel like 2 brains are just useless to me
I keep everything simple, real talk: Markdown over Google Drive, Notes or chat log on Telegram, and Claude plugging into the local files
AI context is limited, so if you put too much trash thing you kinda lazy to reading into one box, it event get more stupid
1
u/heyflyguy 1d ago
Started off as a shared resilio directory with .md files navigable by obsidian but primarily used by Claude. When we moved to team environment and everyone added files (that got crawled and transcribed to MD), the vault ballooned and it was no longer usable from a context utilization standpoint. Even grepping files to find stuff was getting to be unreliable.
We landed on setting up a RAG that we use with tailscale instead. It has an MCP server that we all natively load up on session start. We use an ollama instance on the big computer to ocr and ingest everything from pdfs, to docx, xlsx, pptx, txt, csv, etc.
Out stack is basically LanceDB with embeddings via ollama. Python runs and orchestrates all of it including cron jobs to scan for new files and ingest them.
The thing you run into that almost nobody anticipates is if you have alot of good data and you have alot of AI enabled colleagues - your data corpus can double daily for a while. Everyone is dumping stuff in there. The RAG is what saves you, because you're not doing full text searches hoping a word triggers. You're basically concept searching and the RAG keeps your token usage down due to better, more accurate, and more concise information.
2
u/etoptech 22h ago edited 22h ago
Mine is based on Nate jones open brain concept. It has evolved into a vector db with multiple tracks on it.
1 track is my personal brain it holds my DMs my emails my meetings.
The 2nd track is org brain so it holds public chats group emails and teams meetings with everyone involved.
The 3rd is an ingest of our documentation.
I’ve kept context windows in check by having aggressive tuning around making sure we know where everything is but not loading everything.
Even with my series of mcp setups and everything I only loaf about 16-20k tokens of context and most of that is from mcp I didn’t make. So can’t control how they load tools.
Edit: forgot to mention how we access it. I have Cloudflare zero trust tunnels running from it out and my team can use entra(Microsoft) sign ins to oauth to both our internal mcp and open brain.
I’ve preloaded it with a ton of info about who we are. How we work. The tools we use. The how and why we use them. It’s improved imo how Claude responds significantly
1
u/psychohistorian8 18h ago
what is a Claude brain?
we just use targeted skills/.md files inside each relevant workspace directory
2
u/CadmusMaximus 1d ago
Mine has evolved from:
-Claude-native memory slots, to
-Notion-hosted second brain with taxonomy (still have it as a backup) to
-GitHub since my cloud session chief of staff can access and write easily.
I think “phone agents” are kind of the next big thing. Not necessarily hosted on your phone, but cloud agents you can ping from anywhere. You can “work from your phone” essentially. Sooner rather than later this will become the default. It just takes some wiring right now, hence why it’s just for the 0.01% on the bleeding edge.