How the agent uses knowledge
The agent answers from your systems and from the knowledge base. This page explains what that knowledge base holds. It also explains what you see when the agent searches it.
How does knowledge reach a reply?
What is in the knowledge base?
Your administrator decides what goes in. Hyground imports the documents your organization already writes. Typical content is wiki pages, documentation files from your repositories, files from your artifact repository, and single uploaded documents.
You do not add content to the knowledge base from a session. To give the agent a document for one session, attach it to your message instead. See Upload files. Ask your administrator about what the knowledge base holds.
What is not in the knowledge base?
- The live state of your systems. The agent reads that through tool calls, not from the knowledge base.
- Anything your administrator did not import. Source code and personal notes are common examples.
- Changes made after the last import. The content is as recent as that import, not as recent as today.
- Your own sessions. Those are a separate source. See What the agent remembers.
When does the agent search it?
The agent searches the knowledge base while it writes your reply. It decides by itself when a search helps. A question about your own environment often starts one. A question about a general topic often does not.
Hyground gives you no control that starts or stops this search. The agent decides, and your wording influences that decision. Every search happens inside the reply you are waiting for.
How do you see a search?
Each search appears as one row in the Tools panel. A row begins with the reason for the search. The book icon marks it.
-
Click Tools above the reply. The panel opens.
-
Find a row with the book icon.
-
Click Show command on the row. It shows the words the agent searched for.
-
Click Show response to read what the search returned. Reload the page if the row shows no Show response.
The response lists the pieces of text that matched. Each piece names the document it came from. For the rest of the panel, see What is in the Tools panel?.
The reply itself does not label its sources. Ask the agent directly instead. See Ask the agent for its source.
Why does an answer stay generic?
The agent finds only what the knowledge base holds. A thin knowledge base changes what you get back. Tell your administrator which document is missing.
For the symptom and the checks, see The answer stays generic.
What comes next?
- What the agent can see lists every source of a reply.
- Check the agent's work explains how you verify one.
- Where answers go wrong lists the other failures that can happen.