Brain
Teaching the Brain
Paste what you know, upload a file, drop a link, or import what another AI assistant already knows about you — Dhanu reads it and proposes the pages it should become.
You do not write Brain pages one by one from a blank editor. You teach it: give it material, and it proposes the pages that material should become.
The composer at the centre of Brain has three modes — Teach the brain, Search the brain, Ask the brain. This page is about the first.
Four ways in
| Source | Good for |
|---|---|
| Type or paste | What is in your head, or a chunk of an email or chat |
| A file | PDFs, Word documents, markdown and text — the handbook, the policy set, the process notes |
| A link | A web page or an online doc you want captured |
| Import from an assistant | What ChatGPT, Claude Code, Codex, OpenClaw or Hermes already knows about you |
The last one is worth knowing about: Dhanu gives you a prompt to paste into the other assistant, asking it to dump what it knows about your identity, your work, your projects, your standing preferences. You paste the result back in, and years of accumulated context arrive in one go instead of being retyped.
What happens next
Teaching runs as a background job — you can navigate away and come back. Dhanu reads the material and works out:
- which new pages it should become
- which existing pages it already matches, so nothing is duplicated
- what it should link to, following the categories your workspace uses
The result is a set of proposed pages. Nothing is silently written into your knowledge base because you dropped a file on it.
If review is switched on, those proposals wait for an owner or admin — see Reviewing what it proposes. If it is off, approved pages land directly and you can still edit or delete any of them.
Source pages
If your workspace keeps them, each taught file, link or note also becomes a source page that links to everything it produced. That is your provenance trail: months later you can see the document a fact came from rather than trusting that someone got it right.
What to teach first
Start with the questions people actually ask, not with the biggest folder you have:
- What is our refund window?
- Who approves an expense over one lakh?
- What is the notice period?
- Which client does this contact belong to?
Five good pages beat two hundred uploaded PDFs, because an answer is only as good as what can be found and trusted. The full workflow is in Get your team’s knowledge into Brain.
Working with it well
Teach one subject at a time. A forty-page handbook dumped in one go proposes a wall of pages nobody wants to review. Split it into the questions it answers.
Say what the material is. A line of context before the paste — “this is our 2024 leave policy, it replaces the one from 2021” — changes what gets proposed and how it is linked.
Teach corrections, not just additions. “Sita moved from support to engineering in June” is a perfectly good thing to teach; the review step is where it gets merged into the page that already exists.
Do not paste secrets. Brain is visible to the workspace. Credentials, keys and personal data about individuals belong somewhere with narrower access.