Knowledge

Knowledge holds the reference material your agents draw on. A glossary is a set of domain terms, each with a description and the synonyms it goes by, so the agent recognises what a term means inside your business rather than inferring it from general usage. Collections are not yet available.

Glossaries belong to the project. You write one here and attach it to any agent from the Context step of its configuration, or assign it to agents as you save.

Glossary

Writing a glossary

A glossary is JSON. terms is a map keyed by term id, and an id on the glossary itself is optional. Every term needs a name and a non-empty description, and may list synonyms as an array. Synonyms are what connect the words your customers actually use to the term you have defined, so they are worth filling in even when the canonical name seems obvious.

Insert template gives you the shape with two example terms. Preview renders your JSON as the same table you get once saved, listing every term with its description, synonyms, and id, which is the quickest way to confirm a term has not been lost to a syntax error.

Config holds arbitrary JSON attached to the version. It travels with that version and is available whenever the item is fetched, which makes it a place for metadata such as parameters your own tooling reads.

Associated Agents assigns a version to one or more agents while you save it. The agent label is written onto that version and the agent's configuration is updated to reference it, so an agent runs the version you assigned rather than automatically following the newest one. Assignments can be changed later.

Versions and labels

Every save creates a new version instead of overwriting the current one, and the panel on the left lists them all with the author and date. Each card also carries the labels on that version and the agents using it, so you can see which revision is actually in play before you change anything. A glossary can be shared by several agents. Versions cannot be edited in place, which is what keeps the history trustworthy. New starts another version from the one you are viewing, and the commit message is what makes that history readable months later.

latest is applied automatically and always points at the newest version. Every other label is yours to create and move: the label control on a version opens Context version labels, listing the labels already in the project with a field for adding a new one.

The detail view

Five tabs sit above the content.

• Context shows the item itself, rendered for its type.

• Config holds the arbitrary JSON attached to this version.

• Linked Generations lists the observations that used this version, with the same filters, columns, and export controls as Observability. This is how you tell whether a version is actually being exercised in production, and how it performs when it is.

• Use Context gives you a ready-made Python snippet for fetching the item, either by label or pinned to a version number. Every context type is fetched with get_prompt and its full path.

• Label History is an audit log of label movement: which label changed, whether it was added or removed, the version it landed on, who moved it, and when.

Metrics, in the top right, swaps the versions panel for a table comparing every version side by side: median latency, median input and output tokens, median cost, how many generations used it, and when it was first and last used. It is the fastest way to catch a version that got slower or more expensive before you promote it.