Skip to main content

​
What Are Knowledge Bases?

Knowledge Bases let you upload organizational documents — runbooks, API docs, style guides, internal references — and make them available to Channels and Threads. When a knowledge base exists, its documents are mounted for every agent working in a project it is scoped to, so they can read and search them during any investigation. Access Knowledge Bases from Settings → Context → Knowledge Bases in the sidebar.

​
Creating a Knowledge Group

Knowledge is organized into groups. Each group is a collection of related documents with shared metadata.
Managing Knowledge Bases requires editor or owner permissions in the organization.
  1. Navigate to Settings → Context → Knowledge Bases
  2. Click Create Group
  3. Fill in the group details:
  1. Click Create

​
Uploading Documents

Once a group exists, upload documents to it:
  1. Open the knowledge group detail page
  2. Click Upload Document
  3. Choose the destination folder, or create one with Add folder
  4. Click Choose files to stage several files at once, or Choose folder to bring a folder in from your computer with its structure intact
  5. Click Upload
Supported formats: any file type. Text of PDFs, Word documents, spreadsheets, and slide decks is extracted on upload so agents can search it; plain text formats such as .txt, .md, and .csv are indexed as they are. Other file types (such as .gif) will be stored and available for search by title only (not by content). Maximum file size: 10 MB per document, up to 10 files per batch Plain text documents are normalized to UTF-8 with LF line endings on upload. Each staged file shows whether it is ready or why it was skipped.

​
Managing Documents

Documents are listed by folder. Each folder expands to show what it holds, and the structure you uploaded is preserved. From the knowledge group detail page, you can:
  • Download — Retrieve the original document
  • Delete — Remove a document from the group (requires confirmation)
To delete an entire group, use the Delete Group button on the group detail page.

​
How Agents Use Knowledge Bases

Every knowledge base can be scoped to all or to only specific projects. Agents treat them as first-class context, so a task that touches a base’s documents is answered with them and with the relevant code, memories, etc. in mind. Agents also search knowledge bases by meaning. A natural-language query returns the passages that answer it, each with the document it came from.
Agents only have access to knowledge groups scoped to their project. If a group is restricted to specific projects, agents in other projects will not see it.

​
Letting Agents Write Back

Agents can write to a knowledge base as well as read it. The Allow agents to write switch on a group controls this, and it is on when you create one: agents can add, edit, and delete documents in that group, which is how what one investigation learns becomes context for the next one instead of ending in a chat log. Every workflow also has a knowledge base of its own, named after the workflow. Only runs of that workflow can write to it or read it, and what they leave there outlives the run, so each run starts with what earlier runs worked out. It is managed by PlayerZero rather than listed alongside the groups you create.

​
Filtering and Sorting

The knowledge groups list page supports:
  • Search — Filter by group name or description
  • Category filter — Show only groups in a specific category
  • Sort — By name or most recently updated

​
Get Started

👉 AI Player overview 👉 Hive Mode 👉 Setup guide