> ## Documentation Index
> Fetch the complete documentation index at: https://docs.2501.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Knowledge Base

> Upload documents and let the engine extract reusable knowledge for your agents

The Knowledge Base turns your existing documentation into knowledge your agents can use. Upload runbooks, network diagrams, inventory spreadsheets, and procedures, and the engine automatically parses each document and extracts reusable operational knowledge.

You manage the Knowledge Base in **Command Center** → **Knowledge**.

<Frame caption="Knowledge: drag and drop files onto the page or use the Upload button. Each document is processed as its own ingest job.">
  <img src="https://mintcdn.com/2501/kr0HtinaCJPsc_vr/images/knowledge_list.png?fit=max&auto=format&n=kr0HtinaCJPsc_vr&q=85&s=f844cff21754bd187a20c38e8fe74d43" alt="Knowledge page" width="2880" height="1800" data-path="images/knowledge_list.png" />
</Frame>

## Uploading Documents

Drag and drop files onto the Knowledge page, or use the file picker to select one or more documents at once. Each file is processed as its own ingest job.

**Supported file types:** PDF, DOCX, CSV, and Markdown.

**Maximum size:** 200 MB per file.

<Note>
  When you upload several files together, each one becomes a separate ingest job with its own status. Documents are processed two at a time per organization, in the order you uploaded them, and the rest queue and start as slots free up. A step that runs too long is automatically timed out so the queue keeps moving.
</Note>

## Processing Status

Each document shows its live status as it moves through the pipeline:

| Status     | Meaning                                                             |
| ---------- | ------------------------------------------------------------------- |
| Uploading  | The file is being transferred to the engine.                        |
| Parsed     | The document has been read and its text extracted.                  |
| Extracting | The engine is pulling out rules, blacklist entries, and host facts. |
| Done       | Processing is complete and the extracted knowledge is available.    |
| Failed     | Processing could not complete.                                      |
| Canceled   | You canceled the ingest before it finished.                         |

You can cancel an in-progress ingest at any time, or delete a document once it is done.

## What Gets Extracted

From each document the engine extracts three kinds of knowledge:

* **Operational rules**, directives that guide agent behavior. These appear alongside any rules you create by hand. See [Operational Rules](/0.7/configure/operational-rules).
* **Blacklisted commands**, forbidden commands that agents must not run. These appear alongside your manually created entries. See [Blacklist](/0.7/configure/blacklist).
* **Per-host facts**, details about specific machines, such as roles, IPs, VLANs, and procedures tied to a host.

### How Host Facts Are Matched

Host facts are matched to machines in your inventory by name, IP, or alias. When a fact maps to a known [host](/0.7/core-concepts/hosts), it is attached to that host. Facts that cannot be matched to a known host are still kept so you can review them and reconcile them with your inventory later.

## PDF Vision Captioning

Network documentation often lives in diagrams rather than text. When a multimodal (vision) [model](/0.7/configure/models) is configured for your tenant, the engine describes images embedded in PDFs, along with diagram and scanned pages, and folds those descriptions into the extracted content. This means topology, IP addresses, and VLANs drawn in diagrams are captured rather than lost.

<Note>
  Without a vision model configured, PDFs are processed as text only. Diagrams and scanned pages will not contribute their visual detail to the extracted knowledge.
</Note>

## Re-Uploading and Deleting

### Re-Uploading

Re-uploading a document with the same name supersedes the previous version. The old document's extracted rules, blacklist entries, and host facts are removed and replaced by the new version's results.

<Warning>
  Rows you created or edited by hand in Command Center are never touched by re-ingest. Re-uploading only replaces knowledge that was extracted from that document.
</Warning>

### Deleting

Deleting a knowledge document also deletes every operational rule, blacklist entry, and host fact that was extracted from it. Manually curated rows are left intact.

## How Agents Use Knowledge

Extracted host facts and the per-host **Knowledge** field (shown on each [host](/0.7/core-concepts/hosts)) are automatically provided to agents at task time. Agents can also pull additional relevant rules and host facts on demand while working through a task, so the most pertinent knowledge is available without overloading every task with the entire Knowledge Base.