Skip to content

Tune the catalogue

Use Settings › Catalogue to see and adjust how OpenLatch recognizes what an agent action does and what it touches. Intent policies are written in terms of what actions do, such as reading a credential or pushing code; the catalogue is what maps a concrete tool, program or target to those terms. Every role can read it; only an admin can add or change entries.

The Catalogue settings page of the OpenLatch console, in the Crispy Pay demo organization.The Catalogue settings page of the OpenLatch console, in the Crispy Pay demo organization.
Settings › Catalogue: the tools, programs and targets OpenLatch recognizes, with each entry's effect and source.

The catalogue has three tabs:

TabWhat its entries recognize
ToolsThe tools an agent calls
ProgramsThe programs an agent runs in a shell
TargetsWhat an action touches, such as a file, a host or a repository

Each entry shows its key, its effect, its source and when it was added. Entries come from several sources: OpenLatch’s own seed, learning from your agents’ actions, policy authoring, or an admin. Needs review filters the entries that wait for a decision, and Show OpenLatch seed adds the read-only seed entries to the list.

Learned entries apply to an intent policy according to that policy’s coverage mode; see Write an Agent Intent Policy. An empty catalogue fills as OpenLatch learns the tools, programs and targets your agents use.

ToDo this
Add what OpenLatch does not recognize yetChoose Add entry, and give the key and its effect
Change what a learned entry meansChoose Override on the entry
Make a seed entry stricter for your organizationChoose Narrow on it. The seed itself is read-only; your entry narrows its key