The Context screen in Agent Base: Ops Map, the knowledge base, and house rules, all current
Company Context

Your business, readable by AI The map you built in Ops Map, served to every agent you use.

AI only works when it sees the business. This is how yours gets seen.

One source, many agents

Claude at a desk, the company agent in chat, a scheduled run. They all read the same map and give the same answer.

An Ops Map install token that lets desk agents search the map locally

Loaded in order

House rules first. Then the map, to place the task in your company. Then only the pages the task touches.

What an agent loads, in order

Pointers, not copies

Context stays at the source. When the map changes, every agent sees the change on its next read.

Context sources, all current

Questions & answers

Where does the context come from?
From your operations map. Mapping builds the picture; this service serves that picture to your agents through one connection.
What happens when the business changes?
You change the map, and every agent reads the new version on its next task. There is no second copy to drift out of date.
What can agents actually see?
What you allow. Access follows your rules, reads are logged, and sensitive areas stay closed unless you open them.
How is this different from the knowledge base?
The map says how the company is put together. The knowledge base says how the work is done. Agents read both, and each links to the other.

Make your company readable It starts with the map.