> For the complete documentation index, see [llms.txt](https://docs.cherry-ai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cherry-ai.com/docs/en-us/cherry-studio/preview/knowledge-base.md).

# Knowledge Base

A knowledge base is like giving AI a**dedicated reference book**: you put your own documents, notes, and URLs into it, and then when chatting, let AI look through this book to answer your questions.

<figure><img src="/files/2e0e6f172dbae09c0becccd2320b16c8cb6596e9" alt=""><figcaption><p>Knowledge Base entry: top left <code>+ Add</code> Create your first knowledge base</p></figcaption></figure>

## What can you do with a knowledge base?

Here are a few real-world scenarios:

* **Company knowledge assistant**: Put product manuals, API docs, and internal standards into it, and when employees ask questions, AI answers automatically
* **Personal information manager**: Put your work notes from previous years, reading excerpts, and archived emails into it, and ask AI, "In which PPT last year did I mention that analysis framework?"
* **Study partner**: Put course materials and papers into it, and let AI help you generate questions by chapter and answer your doubts
* **Contract/regulation quick lookup**: Put laws and contract templates into it, and ask AI about the application of specific clauses

## Why use a knowledge base instead of just throwing files at AI?

Limitations of directly uploading files:

* You have to re-upload every time you ask a question, which is cumbersome
* There is a length limit for a single conversation, so long documents can't fit
* Can't be reused across conversations

**The knowledge base solves all the above problems**: Upload once, then it can be used in any conversation, and it can "precisely extract relevant passages" from a large amount of material to feed to AI.

## How to use it?

* First time using it: see [Complete Knowledge Base Tutorial](/docs/en-us/knowledge-base/knowledge-base.md)
* Want to add images / scanned PDFs: first see [Document Preprocessing](/docs/en-us/knowledge-base/document-preprocessing.md), so AI can "read" the text in images
* Want to know how to choose an embedding model: see [Embedding Model Reference](/docs/en-us/knowledge-base/emb-models-info.md)
* Want to know where data is stored: see [Knowledge Base Data](/docs/en-us/knowledge-base/data.md)

## and combinations with other capabilities

* **Knowledge Base + Assistant**: Attach a knowledge base to a certain assistant, and it will specialize in this field
* **Knowledge Base +** [**Cherry Agent**](/docs/en-us/cherry-studio/preview/agent.md): Let the Agent check the knowledge base on its own during tasks
* **Knowledge Base +** [**Channel**](/docs/en-us/advanced-basic/agent-channels.md): Send an Agent that "knows how to look up company documents" to work in Feishu groups

> Recommended first reading [Concepts Basics](/docs/en-us/advanced-basic/concepts-101.md) Learn about the relationship between the knowledge base and features such as Agent / MCP.

***

### 💡 Get help and submit feedback

If you encounter any questions, bugs, or have suggestions for feature improvements during configuration or use, please refer to [Feedback and Suggestions](/docs/en-us/question-contact/suggestions.md) for the official channels provided.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cherry-ai.com/docs/en-us/cherry-studio/preview/knowledge-base.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.