Brains management
A Brain is the durable, curated knowledge a workspace accumulates. The org Brain is deliberately not one big store — it's composed of smaller, access-scoped mini-brains, and a Group Brain is a named set of member mini-brains. This lets knowledge stay visible only to those cleared for it.
Where Brains are managed
Brains are managed from the left sidebar, not the Admin console:
- Manage Brains — click the ⚙ on the Brains section header. The Manage Brains page opens in the main content area and lists every Brain in the workspace.
- Reorder — as a workspace admin, drag the handle on a row to set the workspace's default Brain order. It's saved on the server and reflected everywhere Brains are listed (the sidebar, pickers).
- Manage — each row has one control, which opens that Brain's detail pane: a summary, openers for each tab of its page (Records, Review, Access, Tools) and, if you can administer the Brain, its settings (rename, description, avatar, archive / unarchive, permanent delete). Someone who can only read a Brain sees the openers alone.
- Create Brain stays in the page header for workspace admins.
- A Brain's page — click a Brain in the sidebar section to open its full page: records, the review queue, access, and tools.
Access is granted to groups, which is the clearance model described in Groups & roles.
📸 Screenshot: the Manage Brains page with the sortable list and a detail pane
Records, promotion, and versioning
- Promote to Brain — findings, docs, and canvases become brain records. On promotion, a record is embedded (vectorised) so it can be found by meaning, not just keywords.
- Semantic search runs over a Brain's records via pgvector.
- Supersession — updating a record creates a new version that supersedes the old one; history is preserved, not overwritten.
- Verify / unverify — records can be marked verified, and a review queue lets a curator work through what's been promoted.
Group Brains and mini-brains
- A mini-brain is an access-scoped store — the unit that groups get cleared on.
- A Group Brain composes several member mini-brains under one name, so a chat can draw on a coherent set of knowledge while each piece keeps its own clearance.
The Brain MCP server
A read-only Brain MCP server ships separately (mcp/brain-mcp). It exposes list_brains, get_brain, search_brain, and get_record over stdio to any MCP client, talking to the running API. It's a retrieval surface — reading and searching Brains, not writing them.
Brain tools (act/write) — coming soon
A Brain can be bound to integrations (see Integrations & plugins), but a Brain invoking a tool — reading a mailbox, querying a database, calling an MCP server — is not built yet. The tool-handler model and the write-tool confirmation UX are pending design decisions. Today Brains are knowledge and retrieval only.