Skip to main content

Extension customization

The extension's interface is fixed. What changes is the configuration behind it and a small set of per-user preferences.

Organization-level settings​

In the Backoffice, under Settings, AI configuration:

  • AI provider: which engine answers, including your own key or an on-premise engine. See Bring your own LLM.
  • AI model: the model used for responses.
  • Tool use: whether the assistant may call tools at all.

What the assistant knows and how it behaves on your application is not a setting. It is your configuration: knowledge, views, controls, forms, action plans and tools. See Authoring for the agent.

Domain configuration​

Which pages the extension has app context on:

  1. Register your domains in the Backoffice.
  2. Map URL patterns to views, and scope knowledge to those views.
  3. On a registered domain the assistant answers with your configuration behind it. Elsewhere it runs in live page mode, grounded in the page and your organization's own knowledge.

Two things override all of that. A user can pause Appilot on a site from the page's context menu, and the extension does not mount on Appilot's own hosts at all: the public site, this documentation, the downloads page, and the My Account and Backoffice consoles. Matching covers subdomains, so one host covers a whole site.

Turn scope​

A turn belongs to the tab it started in. The tab is fixed when the user sends, and every read and action during that turn goes there, so a user switching tabs while the assistant works does not redirect it. If the tab is closed or navigates to another origin, the assistant refuses the read rather than acting on the new page. Build integrations on the assumption that the turn cannot follow the user to another tab.

User-level settings​

In the panel's menu, under Settings:

  • Language: English, Spanish or German.
  • Theme: light or dark.
  • Panel side: which edge the panel opens on.
  • Page Inspector: a troubleshooting view showing what Appilot detected on the current page, and where each element is.
  • My context: personal information the user chooses to make available to the assistant, editable in My Account.

Pausing Appilot on the current site is on the page's context menu rather than in this panel, because that is where a user reaches for it.