For the complete documentation index, see llms.txt. This page is also available as Markdown.

Interface

Let the Agent read your own product's pages so it can answer questions about what users actually see on screen, element by element.


Dashboard path: Agent > Knowledge > Interface

Sources teach the Agent what your documentation says. Interface teaches it what your product is: the screens, buttons, filters and menus your users are looking at when they ask for help.

Two ways the Agent can learn a page

When you add a page, Jimo asks: How should your agent learn this page?

Mode
What it does
Time
Control

Scan and curate

Catalogs the elements on the page. You review everything before the Agent uses it.

~3 mins

You curate

Read all

The Agent reads the page in real time whenever a user asks about it. No setup.

Instant

Sees live

Scan and curate is the right choice for your core screens: you decide element by element what the Agent can read, write what each element does, and attach Skills to the page. Read all fits long-tail pages where instant coverage matters more than curation.

Enabling Read all

Read all is the same thing as turning Trusted Page on for that page: the Agent gets full live access and can read any element on the fly, without a catalog. Because of that, Jimo asks you to confirm you understand before enabling it, then shows a confirmation screen with two ways to continue: Test Chat, or Set up skills.

Read all means the Agent sees what the user sees, live.

You can switch a page from one mode to the other at any time, from the Trusted Page toggle in Page details.

The pages list

Each scanned page appears as a card with its screenshot, name, and two counters: the number of Elements the Agent can read, and the number of Skills attached to the page.

Use the search field to find a page, and Scan a page (top-right) to add one. See Scan a page. There is no limit on the number of pages you can add.

Clicking a card opens the page's detail panel: its elements by category, its Skills, and its URL rules. See Page details.

In this section

  • Scan a page: capture a page's elements, interact to uncover more, and save

  • Page details: curate what the Agent reads, element by element

  • Knowledge: the five kinds of Agent knowledge

  • Skills: procedures that run on the pages the Agent knows

  • Sources: the documentation side of the knowledge base

Last updated