Sources · Company source · export guide
Link a Git docs repository to a Company Brain
Not an export: a repository you already have, read in place. Every document becomes a note in a generic taxonomy, with versions and duplicates grouped — and files with credentials never enter the brain.
What a Git docs repo export holds — and what the brain makes of it
Clone the repository to your computer and link the folder from Studio’s Sources (nothing is copied, nothing in the repository is changed, and the .git folder is never written). The brain builder reads every document — Markdown, PDF, Word, Excel, PowerPoint, images, code — and files it under strategy, product, engineering, customers, sales, finance, legal, compliance or marketing, with its document type and the customer or vendor it concerns. Version chains, byte-identical duplicates and md-to-pdf renders are grouped; authors (names only) and dates come from the repository history.
Before any file is read, a deterministic local scanner (no AI) tiers it. A file that carries credentials, keys or dense personal data becomes a metadata-only note — its name and place are known, its content never enters the vault. PDF text is extracted on a best-effort basis; there is no OCR.
Step by step
How to link Git docs repo
Nothing is copied and nothing in the folder is changed: the brain reads it in place.
- 01
Clone the repository to this computer
- 02
Studio → Sources → Git docs repo → Link folder… (nothing is copied or changed)
- 03
Reseed
- 04
Press Reseed in Studio — or tell Claude Code or Codex “build my brain from this”. The source is detected by itself, even inside a combined archive.
Then, next month
An export is a snapshot. Drop a newer one and press Update: your edits and _notes/ are kept, and the update report says what changed.
Then ask it
What you can ask a brain built from Git docs repo
Examples, not promises: the answer is whatever your notes hold, and every answer cites the notes it came from. The more exports you add, the more these questions cross sources.
- Which runbooks mention the payments service, and when were they last changed?
- Which customers have a proposal in the repository, and who wrote it?
- Which documents exist in three versions, and which is current?
limitA linked folder is read at build time; change the repository and press Update. Files the scanner tiers as sensitive stay metadata-only — by design, not configuration.
Good to know
The honest answers.
Does it upload the repository? No. The folder is linked read-only on your machine; the build makes zero network calls. For a remote repository, the separate docs-connector plugin clones it to a mirror outside your data folder first.
How are secrets kept out? A deterministic local scanner (rules you can read, no AI) tiers every file; files with credentials, keys, archives or dense personal data become metadata-only stubs. The honest claim is "kept out by a local scanner", nothing stronger — PDF extraction is best-effort, with no OCR.
Start
Your company’s exports already exist. Turn them into a brain.
Free and open source on your own machine. Or hand us the exports — done-for-you onboarding is in early access.
Second Brain Studio · Mac (Apple silicon and Intel), Windows and Linux · free · MIT
Just looking? Open Studio in your browser — two demo brains, nothing to install