# Knowledge

Source: https://www.hyperagent.com/docs/knowledge

> For AI agents: the documentation index is at https://www.hyperagent.com/llms.txt and the complete documentation in one file at https://www.hyperagent.com/llms-full.txt. Any docs page is also served as Markdown by appending `.md` to its URL.

The facts, methods, and reference material agents can use across work, and the controls that decide where each belongs.

A Customer Success agent preparing a renewal brief should not need the same setup every time. It can remember how leadership wants risk framed, follow the team's account-review method, and open the customer history and usage table when the work calls for them. **Knowledge** is the material that lets an agent begin from what your team has already established.

Preserve the facts, methods, and reference material worth using again. The
next thread can retrieve the right context without carrying every prior
conversation with it.



## Three kinds of knowledge [#three-kinds-of-knowledge]

Preferences, decisions, definitions, relationships, and other standing
context the agent should be able to recall in future work.

Repeatable ways of doing work: the checklist, format, decision rules,
scripts, and when-to-use guidance behind a reliable result.

Written material and structured records the agent reads, updates, and reuses across
threads, such as a brand guide, research brief, account tracker, or dataset.

## Knowledge is what you give an agent to work from [#knowledge-is-what-you-give-an-agent-to-work-from]

Knowledge is the material an agent begins from instead of rediscovering: a memory it recalls, a skill it follows, a document or table it reads. Some of it you lift out of real runs, a fact you corrected or a method that worked. Just as much of it you bring in from outside: upload a brand guide, write a memory by hand, attach a dataset the agent should treat as ground truth. Either way, giving an agent knowledge is deliberate.

That is also the property that separates knowledge from a thread's own history. A [thread](https://www.hyperagent.com/docs/concepts/threads) keeps the conversation and tool results for one piece of work, and the next thread does not inherit them. Knowledge is what you deliberately keep or provide so the next run can use it, there for work that hasn't started yet.

## Work creates knowledge, and you decide what lasts [#work-creates-knowledge-and-you-decide-what-lasts]

A run often reveals something worth keeping: a fact you corrected, a method that worked, reference material worth keeping current. The agent proposes a memory, skill, or prompt improvement, and nothing becomes standing knowledge until you accept it, unless you've allowed a trusted agent to save that kind on its own. Documents and tables the agent builds are editable outputs that live in the Library. See [Learning](https://www.hyperagent.com/docs/learning) for how proposals are raised and reviewed.



## The agent loads only what a run needs [#the-agent-loads-only-what-a-run-needs]

Saved knowledge is not poured into every run. A small amount of pinned context arrives up front; the rest surfaces or is fetched when the conversation makes it relevant, so the [context window](https://www.hyperagent.com/docs/concepts/threads/index#when-the-work-changes-start-a-new-thread) stays free for the work itself. This is why what an agent *can* reach and what it *loads* on a given run are different things. See [How context gets into a thread](https://www.hyperagent.com/docs/concepts/threads/loading-context).

## Choose the right home [#choose-the-right-home]

Match what you are preserving to the question it answers. This keeps one fact from becoming a document, one process from becoming a memory, and one run's temporary state from leaking into every future job.

| You need to preserve                                                  | Put it here                                                      | Example                                                                                     |
| --------------------------------------------------------------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| A standing fact, preference, correction, or relationship              | A [memory](https://www.hyperagent.com/docs/concepts/memories)                              | “Renewal briefs should lead with risk and next action.”                                     |
| A repeatable process or quality standard                              | A [skill](https://www.hyperagent.com/docs/concepts/skills)                                 | “How to prepare and review a renewal brief.”                                                |
| Written material the agent reads or maintains                         | A [document](https://www.hyperagent.com/docs/knowledge/documents-and-tables)               | A living customer brief or brand guide.                                                     |
| Structured records with reusable columns                              | A [table](https://www.hyperagent.com/docs/knowledge/documents-and-tables)                  | Account health, owners, renewal dates, and status.                                          |
| Facts, corrections, decisions, and plan details for this conversation | [Thread Context Document](https://www.hyperagent.com/docs/concepts/threads/thread-context) | “For this run, use the corrected renewal date of October 12.”                               |
| Data that already belongs in another system                           | Keep it in the connected system                                  | Current CRM fields, support tickets, or calendar events the agent can retrieve when needed. |

## Control who can use and change knowledge [#control-who-can-use-and-change-knowledge]

[Knowledge and learning](https://www.hyperagent.com/docs/concepts/agents/knowledge-access) controls
which memories the agent can read, whether it can discover skills, which
context files travel with it, and where new learning is saved.

[Learning](https://www.hyperagent.com/docs/learning) collects proposed memories, skills, prompt
improvements, and configuration changes. Review the suggestion before it
becomes lasting knowledge, or allow trusted personal agents to save selected
types automatically.

## FAQs [#faqs]

Use a memory for a fact or preference, a skill for a reusable method, and a document or table for material the agent should read or maintain. Leave temporary facts and the current plan in the Thread Context Document. If the information already has an authoritative home, such as a CRM or support system, keep it there and let the integration retrieve it.

Each agent has its own knowledge boundary. The memory may belong to agent A, the skill may not be attached or discoverable to agent B, or the material may still live only in the original thread. Open agent B's [Knowledge and learning](https://www.hyperagent.com/docs/concepts/agents/knowledge-access) settings to check its access.

No. Agents can propose memories, skills, and other improvements as they work, and trusted agents can auto-save selected learning types. Review remains important: keep stable, reusable context and dismiss chatter, temporary facts, and duplicates. See [Suggestions and auto-learning](https://www.hyperagent.com/docs/learning/manage-suggestions).