Skip to main content
A Company Brain, often shortened to a Brain, is a shared knowledge base that gives your agents trusted context from across your organization. Use one to make product documentation, internal policies, customer knowledge, research, or other reference material available to multiple agents without copying the same files into every project.
Builders create and manage Brains in Studio under Brains (/brains). To share a Brain with every Space at once, owners and admins use Governance → Organization knowledge (Governance settings).

​
What a Brain does

A Brain turns a collection of documents and other source material into context that agents can search and read when a task requires it. Instead of placing every document in an agent’s prompt, Luno OS indexes the content and gives the agent retrieval tools. The agent can:
  • Search across the available knowledge using meaning and keywords
  • Read the relevant part of a source before answering or taking action
  • Filter knowledge by metadata, such as team, source, customer, or document type
  • Use the same managed knowledge across multiple projects and agents
  • Work from updated sources as documents are added, changed, or removed
For example, a support agent could search a Brain containing product documentation and support policies. A sales agent could use a filtered view of the same Brain for approved positioning, pricing, and customer-facing material.

​
How Brains work

At a high level:
  1. Add knowledge. Upload or sync documents, structured content, and other supported sources into a Brain.
  2. Index the content. Luno OS extracts text, divides it into useful sections, and builds a searchable index.
  3. Share access. Choose which projects and agents can read or manage the Brain.
  4. Retrieve when needed. An agent searches the Brain for relevant sections, then reads the source material it needs.
  5. Keep it current. When source content changes, Luno OS updates the index so future searches use the latest available version.
Each Brain has a name and description that help an agent choose the right source. When an agent has access to more than one Brain, clear descriptions make it easier to search the appropriate knowledge base for the task.

​
Organize shared knowledge

A Brain owns a set of documents, and filters expose narrower views based on metadata. A view can make only part of a larger knowledge base available without duplicating its documents. For example, one company-wide Brain could contain material from several departments, with separate views for:
  • Product and engineering documentation
  • Brand voice and approved marketing claims
  • Finance policies and planning context
  • Customer support procedures
  • Sales enablement material
Access can be granted at the organization or project level so teams can share common knowledge while limiting sensitive or specialized sources.

​
Brains compared with files, memory, and skills

These features all provide context, but they serve different purposes: A Brain is useful when the source material is too broad or frequently changing to attach as static files, or when several agents need access to the same managed knowledge.

​
Manage Brains in the web app

Studio → Brains lists every Brain you can see with its sources, documents, status (Indexing, Reindexing, or Some documents failed / Indexing failed when documents could not be indexed; open the Brain to see why) and the Spaces that use it. Add Brain creates one; click a row for what is inside, or open a Brain’s page for its Overview, Filters, Spaces (which Spaces can read or write it), Managers and Settings tabs. Explore the graph opens the Brain’s knowledge graph (Graph tab: the people, organizations, places, products, concepts and events found in its documents and how they connect) next to a Documents tab. Settings → Knowledge graph turns graph extraction on or off; Settings → Reindex rebuilds the search index and the graph. To build Brains in code (uploads, sync workflows, filters), see Brains.