Getting started
Add-ons.
Code from other developers that adds to Kaleta – how to install one safely, and where developers start.
Extensions are parts of Kaleta you switch on and off. Add-ons are code from other developers – a statistics service, a widget, an integration Kaleta does not have.
Before you install one
An add-on runs with the same rights as Kaleta itself, like a plug-in in WordPress. Install only code you trust, from a source you know. Kaleta never uploads or downloads add-ons on its own.
Install
- Copy the add-on's folder into
extensions/on your hosting (e.g.extensions/hello/). - In Administration → Add-ons you see it with its version and what it needs. Tick I trust this code and Switch on.
- Its own pages appear under Add-ons; its tools are available to Claude with the connection's access and your guardrails.
When something goes wrong
- An add-on that fails while loading is switched off at once and Add-ons shows the error.
- An add-on written for another API version or Kaleta version is not loaded and says why.
- If the site is in trouble, the hosting administrator can add
'addons' => falsetoconfig.php– no add-on is loaded until it is removed. - Updates of Kaleta never touch
extensions/; switching an add-on off keeps its data.
For developers
The extension API (version 1) gives an add-on events, filters for the page head, footer and HTML, text tokens, administration pages, tools for Claude, background jobs and settings. It is a recorded contract that holds through 3.x. Start with docs/EXTENSIONS.md and the example add-on in docs/examples/extensions/hello/ on GitHub.