Skip to main content

Legacy Knowledge Bases reference

A legacy Knowledge Base is the previous knowledge system. It is deprecated: existing agents that use one keep working, but it does not receive new features, and new agents should use Knowledge Sources instead.

This page is a lookup for what a legacy Knowledge Base is and how it differs from Knowledge Sources. To move an agent off a legacy Knowledge Base, follow the step-by-step Knowledge Sources migration guide — this page does not repeat those steps.

What a legacy Knowledge Base is​

A legacy Knowledge Base is a named collection of knowledge that you attach to a single agent. It holds sources of several types, including files, websites, video links, and manually entered content.

It differs from the modern Knowledge Sources library in two main ways:

  • It is attached to one agent at a time, not shared. You select one Knowledge Base per agent. Knowledge Sources, by contrast, is a tenant-wide library where one source can be connected to any number of agents — see Knowledge Sources.
  • It is the older system. Knowledge Sources adds the shared library, per-source usage tracking, and the unanswered-questions workflow. See Connect knowledge to the agent for what the modern library offers.

Where the legacy attachment still appears​

The legacy Knowledge Base attachment is still visible in two places.

LocationWhat you see
The General card of an agentA Knowledge base selector marked (Unsupported), with a Legacy Knowledge Bases link. The selector is a single-choice dropdown — you attach one Knowledge Base or clear it.
The agent's Knowledge Sources tab (Simple mode)When the attached Knowledge Base was changed in Advanced mode, the tab shows Unsupported Knowledge Base and viewing and editing there are disabled.

The full Unsupported Knowledge Base message reads: This knowledge base was changed outside of the standard flow (Advanced Mode), so it's no longer compatible with this interface. Viewing and editing are disabled. It links to the legacy knowledge base page and to the migration documentation.

There is no menu entry for the legacy Knowledge Bases list. You reach it from the Legacy Knowledge Bases link in the agent's General card. The modern library is the only knowledge entry in the left menu, under AI Agents > Knowledge Sources.

How it differs from Knowledge Sources​

Legacy Knowledge BaseKnowledge Sources
ScopeAttached to one agent at a timeTenant-wide library, connected to any number of agents
Where you manage itA separate legacy Knowledge Bases page, reached from the agent's General cardAI Agents > Knowledge Sources
Status in the productDeprecated; no new featuresThe current, supported system
Editing after Advanced-mode changesDisabled — shows Unsupported Knowledge BaseNot applicable

For the modern source types, formats, and limits, see Knowledge Source Types and Limits.

The Prefer llms.txt checkbox is legacy-KB-only​

The website source form in a legacy Knowledge Base has a Prefer llms.txt for website parsing checkbox. Its tooltip reads: If an llms.txt file is found on the website, the system will use it to determine which pages to parse instead of performing full website crawling. If an llms-full.txt file is present, only the content from this file will be used and the website itself will not be crawled.

This checkbox exists only in the legacy Knowledge Base website form. The modern Knowledge Sources Websites source has no equivalent option.

Why new agents use Knowledge Sources​

New agents should use Knowledge Sources because the legacy Knowledge Base is deprecated and does not receive new features. Knowledge Sources adds a shared, tenant-wide library so one source can serve many agents, plus per-source usage tracking and the unanswered-questions workflow on the FAQs tab. The attachment in the agent's General card is marked (Unsupported) for the same reason.

To move an existing agent from a legacy Knowledge Base to Knowledge Sources, follow the Knowledge Sources migration guide.

Was this article helpful?