Search by

masilia / ibexa-ai

masilia

AI assistant for Ibexa CMS 5: provider layer, content suggestions, agent with approval flow (Neuron AI)

Package info

github.com/MasiliaLabs/ibexa-ai

Type:ibexa-bundle

pkg:composer/masilia/ibexa-ai

Statistics

Installs: 90

Dependents: 3

Suggesters: 1

Stars: 0

Open Issues: 0

2.4.3 2026-11-20 12:39 UTC

README

CI Latest version Downloads PHP License: MIT

The AI assistant for Ibexa 5: a registry of capabilities that mirror the admin, a chat for editors, an approval flow, and one AI provider per siteaccess.

masilia/ibexa-ai is part of a family of packages for Ibexa that work together or alone. See the other packages.

What it is

An AI assistant for the Ibexa admin, built on Neuron AI (v4). Instead of a few hard-coded tools, it gives the model a registry of capabilities that mirror what the Ibexa admin does — with the same rules — so an editor can ask in plain language and approve each change.

Features

  • Capabilities: more than a hundred, grouped in domains (content, trash, structure, URLs, relations, users and roles…). Each is a Neuron tool, found by the model with tool_search, checked with Ibexa's own rules before it runs.
  • Risk tiers and approval: every capability is read, write, destructive or access. Anything that changes something shows an approval card with a preview; propose_changes groups a batch. What the user's role does not allow is refused before the card.
  • Audit: what the assistant did, for whom, and with what result.
  • A chat in the admin (a floating widget built with assistant-ui over the AG-UI protocol), for everyone whose role has masilia_ai/use. Conversations are kept and can be renamed or deleted.
  • Providers per siteaccess: OpenAI, Anthropic, Gemini, Mistral, Ollama, Qwen, Kimi, MiniMax and MiMo, configured in the admin (AI Assistant page), one provider answering for a siteaccess. API keys are encrypted at rest. A fallback connection can be set in configuration.
  • Two admin pages: AI Assistant (/ai/settings: engine status, providers and models, usage, siteaccesses) and What the assistant can do (/ai/capabilities: every capability, its risk, what it needs, and whether you can use it).
  • Extensible: other packages add capabilities, field inputs and skills through the contracts in Masilia\Contracts\IbexaAi (masilia.ibexa_ai.capability tag). masilia/ibexa-ai-craft and masilia/ibexa-ai-editor are built that way.

Requirements

  • PHP 8.3 or later
  • Ibexa 5.0 (Symfony 7.4)
  • Node.js 24 and Yarn, to build the admin assets with the Ibexa Encore setup of your project

Installed with it by Composer:

Works better with (optional):

Installation

composer require masilia/ibexa-ai
  1. Enable the bundles in config/bundles.php:

    Masilia\Bundle\IbexaAdminKit\MasiliaIbexaAdminKitBundle::class => ['all' => true],
    Masilia\Bundle\IbexaAi\MasiliaIbexaAiBundle::class => ['all' => true],
  2. Import the routes (config/routes/masilia_ibexa_ai.yaml):

    masilia_ibexa_ai:
        resource: '@MasiliaIbexaAiBundle/Resources/config/routes.yaml'
  3. Set an encryption key for the API keys and create the tables:

    php -r 'echo base64_encode(random_bytes(32));'     # put the result in AI_ENCRYPTION_KEY
    php bin/console doctrine:migrations:migrate
    # config/packages/masilia_ibexa_ai.yaml
    masilia_ibexa_ai:
        encryption_key: '%env(AI_ENCRYPTION_KEY)%'

    Without an explicit key, one is derived from APP_SECRET: changing the secret would make the stored keys unreadable. If keys were stored before encryption existed, run php bin/console masilia:ai:encrypt-keys (safe to repeat, --dry-run shows what it would do).

  4. Build the admin assets and give a role the policies. The chat widget imports npm packages that Composer cannot install. Without them the admin still builds: the chat is left out (no launcher in the admin) and the build prints The AI chat is not built: the project does not have .... To have the chat, install them and build again:

    yarn add @ag-ui/client @assistant-ui/react @assistant-ui/react-ag-ui @assistant-ui/react-markdown remark-gfm
    yarn ibexa-generate-tsconfig
    php bin/console ibexa:encore:compile

    Inside DDEV, prefix each command with ddev exec. The admin build is ibexa:encore:compile: yarn encore dev --config-name ibexa does not work ("Configuration with the name ibexa was not found").

    Policy (masilia_ai) Lets the role…
    use open the chat and use read capabilities
    write approve changes to contents
    destructive approve deletions and the like
    structure change the content model (types, groups, fields)
    access manage roles, policies and users (off by default)

    The Administrator role has them all.

With Symfony Flex

The Masilia recipes do the first steps for you. Add their endpoint once to the composer.json of your project, after the one of Ibexa:

"extra": {
    "symfony": {
        "endpoint": [
            "https://api.github.com/repos/ibexa/recipes/contents/index.json?ref=flex/main",
            "https://api.github.com/repos/MasiliaLabs/recipes/contents/index.json?ref=flex/main",
            "flex://defaults"
        ]
    }
}

Then composer require masilia/ibexa-ai enables the bundle and writes config/routes/masilia_ibexa_ai.yaml and config/packages/masilia_ibexa_ai.yaml. What is left is yours: AI_ENCRYPTION_KEY, the migrations, the five npm packages of the chat, the admin build and the masilia_ai policies. The manual steps above and below stay valid.

Configuration

masilia_ibexa_ai:
    # A single provider for every siteaccess, when you do not use the admin page
    connection:
        provider: openai          # openai, anthropic, gemini, mistral, ollama, qwen, kimi, minimax or mimo
        model: gpt-4o
        api_key: '%env(OPENAI_API_KEY)%'
        temperature: 0.7
        max_tokens: 4096
    os:
        domains:
            access: false         # roles, policies and users: off until you turn it on
    encryption_key: '%env(AI_ENCRYPTION_KEY)%'

Providers and models installed

doctrine:migrations:migrate also fills the catalog, so a new project only has to give an API key (AI Assistant, the key of a provider). The migration (Version20261120000000) reads what exists and only adds what is missing: a provider with no row of its identifier is created (without a key), a model the provider does not have is added, and the active chat model is set for the providers it creates. It never changes or removes a row that exists. The list is the one of 2026-11-20, read on the documentation of each provider; models change often, add and remove yours in the admin.

Provider Models (chat unless noted) Active chat model
OpenAI gpt-6.2-astra, gpt-6.2-sol, gpt-6.1-terra, gpt-6-luna gpt-6.2-astra
Anthropic claude-fable-5-2, claude-opus-5-5, claude-sonnet-5-5, claude-haiku-5-5 claude-sonnet-5-5
Google Gemini gemini-3.8-flash, gemini-3.6-flash, gemini-3.5-flash-lite; images: gemini-3.1-flash-image, gemini-3-pro-image gemini-3.8-flash (image: gemini-3.1-flash-image)
Qwen qwen3.7-plus, qwen3.6-plus, qwen3.6-flash, qwen3.5-plus, qwen3.5-flash, qwen-max, qwen-plus, qwen-flash qwen3.7-plus
Kimi kimi-k3 kimi-k3
MiniMax MiniMax-M3.1-Flash, MiniMax-M3 MiniMax-M3
MiMo mimo-v2.5-pro, mimo-v2.5 mimo-v2.5-pro
Mistral, Ollama none: Mistral does not state its API names, Ollama depends on what you pulled none

On a project that already has providers, only the missing models are added (and the providers that are missing); the keys, the active models and the rows you made are left as they are.

Usage

Open AI Assistant in the admin, add a provider (a key, an endpoint for local models), pick its chat model and assign it to a siteaccess. Check again tests the engine. Then open the chat from the floating button and ask, for example, "list the children of the home page" or "create a folder called News under the home page" — the second one shows an approval card.

Checks for developers and for your deployments:

php bin/console masilia:ai:os:coverage [--strict]    # admin routes that no capability covers
php bin/console masilia:ai:os:selftest <locationId>  # runs every capability on throwaway folders, then deletes them

Tests

composer install
vendor/bin/phpunit
vendor/bin/phpstan analyse --memory-limit=2G --no-progress

AI agent skill

This package ships a skill for AI coding agents (Claude Code and other agents that read SKILL.md skills): how to install, configure, operate and troubleshoot masilia/ibexa-ai. It lives in skills/masilia-ibexa-ai and comes with the package.

# For the project (committed with it): from the installed package
mkdir -p .claude/skills && cp -r vendor/masilia/ibexa-ai/skills/masilia-ibexa-ai .claude/skills/

# For all your projects: global
mkdir -p ~/.claude/skills && cp -r vendor/masilia/ibexa-ai/skills/masilia-ibexa-ai ~/.claude/skills/

Restart the agent (or reload its skills) to pick it up. Update the copy after composer update.

The Masilia packages

Package What it does
masilia/ibexa-admin-kit React components in the design of the Ibexa admin, for admin pages
masilia/ibexa-sites A registry of sites that Ibexa serves without a deploy
masilia/ibexa-ai The AI assistant for Ibexa: capabilities, providers, chat, approval flow
masilia/ibexa-ai-craft The assistant builds sites and pages out of blocks
masilia/ibexa-ai-editor AI suggestions and image generation in the content editing form
masilia/ibexa-blocks Front-office rendering of pages made of blocks, with themes
masilia/editorial-toolbox In-context editing toolbar for the front office

What requires what (Composer installs it for you):

  • ibexa-sites requires ibexa-admin-kit
  • ibexa-ai requires ibexa-admin-kit
  • ibexa-ai-editor requires ibexa-ai
  • ibexa-ai-craft requires ibexa-ai, ibexa-blocks and ibexa-sites
  • ibexa-blocks and editorial-toolbox require none of the others; they are happy to find ibexa-sites (and each other) when installed.

Compatibility

Package version PHP Ibexa
latest 8.3+ 5.0

Download

  • Composer (recommended): composer require masilia/ibexa-ai — ibexa-ai on Packagist
  • Archive of a release: GitHub releases (each release lists what changed)
  • Source: git clone https://github.com/MasiliaLabs/ibexa-ai.git
  • What changed between versions: CHANGELOG.md

Stay informed

New versions are announced as GitHub releases, with their notes taken from the CHANGELOG:

  • On GitHub: Watch this repository, Custom, Releases, to be notified of each release; or follow the feed https://github.com/MasiliaLabs/ibexa-ai/releases.atom in your reader.

  • In your project: composer outdated "masilia/*" lists what is behind. To be told by a pull request, let Dependabot (or Renovate) watch the Masilia packages:

    # .github/dependabot.yml
    version: 2
    updates:
      - package-ecosystem: composer
        directory: /
        schedule: { interval: weekly }
        allow:
          - dependency-name: "masilia/*"
  • Before updating: the CHANGELOG says what changes; a change that breaks something is marked Breaking and explained in UPGRADE.md when there is one. Before 1.0, a minor version (0.x) may contain breaking changes: read the notes of the versions you skip. Security problems are announced as GitHub security advisories (see SECURITY.md).

Support, contributing and security

License

Released under the MIT license. Copyright © 2026 MasiliaLabs.

Ibexa itself is distributed under its own licenses (Ibexa OSS: GPL-2.0), which apply to the project that uses this package. This package is an independent project, not affiliated with or endorsed by Ibexa AS; "Ibexa" is a trademark of its owner.