Skip to main content
Conductor can inspect your knowledge bases, their source metadata, and indexing status. Attach a knowledge base or name it in your request to find its sources and understand how it is configured.

​
When to use it

Use Conductor to find an existing knowledge base, check why indexing has not finished, or identify the knowledge bases attached to an agent or node. For example: “Which knowledge bases does my appointment-booking agent use, and have they finished indexing?”

​
Inspect a knowledge base

1

Choose the knowledge base

Open Conductor and use Add context (+) → Knowledge Base. Select an item, or use Multi-select to attach several. You can also ask Conductor to find a knowledge base by name.
2

Ask about its setup

Ask for the source inventory, indexing status, reported errors, or refresh settings. For example: “List this knowledge base’s sources and explain any indexing errors.”
3

Check agent associations

Attach the relevant agent or node and ask which knowledge bases it uses. To compare agents, attach both and ask how their knowledge-base configuration differs.
See Give Conductor context for selecting resources across your workspace.

​
What can Conductor inspect?

Conductor can list knowledge bases and read their names, source metadata, indexing status, error messages, and refresh configuration. Source metadata includes information such as URLs, filenames, and titles. A source count may be incomplete while indexing is in progress or has failed. Ask Conductor to check the status before interpreting a missing source as an empty knowledge base.

​
Can Conductor read or change the source content?

Conductor’s knowledge-base tools cannot search or read indexed source contents, create a knowledge base, or add, replace, or delete its sources. Manage those changes on the Knowledge Base page. To discuss the contents of a specific document, attach the file to your message. Attaching a knowledge base provides its configuration and source metadata.