Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,110 of 9,110 pages
About the help in other languages
All help pages

Extending the assistant

An overview of what an extension can add to Exponential Intelligence without changing it - field actions by settings only, tools the model can call, read services that opt in, providers, panel and edit form sections and…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/ai-agents/expai/extending-the-assistant.md

On this page

Extending the assistant

This page is for developers who want Exponential Intelligence to do something specific for their site. Everything is added from your own extension, by settings and small classes; the assistant itself stays unchanged. The task guide with code is Extending Exponential Intelligence; this page is the overview.

Contents

  1. What you can add
  2. Rules every addition keeps
  3. Choosing the smallest addition
  4. Checking your additions

What you can add

AdditionHowExample
A field actionSettings only: [EditViewSettings] FieldActions[] and a [FieldAction_<id>] group with label, datatypes, input and instructionA "Headline" button on text line fields
A tool the model can callA class extending expAiTool, listed in [ToolSettings] Tools[]Counting children of a node
A read service as a tool'ai' => true in an expservices declaration, no classService tools
A providerA [Provider_<id>] group for an OpenAI- or Anthropic-compatible server, or a class implementing expAiProviderA company's own model gateway
Panel and edit form sectionsTemplates your extension adds to expai's listsA section with house-style hints
JavaScript hooksScript files in your design's backend script list, without inline scriptsReacting when a draft is written

Rules every addition keeps

From the expai extension documentation:

  • Read and write through the context's reader and writer, which run as the current user with the kernel's checks.
  • A writing tool records its drafts and never publishes.
  • Errors the model should hear are thrown as the assistant's own exception type, so the model can correct its call.
  • New tools are offered in new conversations.
  • Admin templates and scripts keep the admin rules: no inline scripts or styles, so the Content Security Policy holds.

Choosing the smallest addition

  1. Can a field action by settings do it? Then no code is needed.
  2. Does a read service already return what the model needs? Opt it in.
  3. Only then write a tool class.
  4. Only for an incompatible API write a provider class; compatible servers need settings only.

The smaller the addition, the less there is to review, and the fewer ways a model can misuse it.

Checking your additions

expai declares its registries for the RAD tools: Setup > RAD > Extension point survey counts your providers, tools and field actions and shows any whose class, template or block is missing (RAD extension surface). Then activate the extension, regenerate the autoloads, clear the caches, and try the addition with a test editor.

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x