Add optional AI capabilities

Created on 29 August 2024, 4 months ago

Problem/Motivation

To make it possible to use certain pieces of functionality from the AI, AI Image Alt Text and AI Agents module we need to have a recipe to install this, but also set this up.

Since AI in many cases uses external and propitiatory models, it will be setup so its an optional form step where you can choose one of the easy-to-use providers like Anthropic and OpenAI + API Keys or the default choice will be that no AI provider will be installed. For more complex self hosted providers like LLM Studio or Ollama, they would have to be setup post-installation.

The recipes itself, will install everything, but the chatbot block and assistant will be removed and the AI Image Alt Text module will be uninstalled if no AI Provider is set.

It should be split up in two recipes, one for the AI Image Alt Text and one for the Assistant/Chatbot/Agents.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request
Status

Active

Component

Track: AI

Created by

πŸ‡©πŸ‡ͺGermany marcus_johansson

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @marcus_johansson
  • Pipeline finished with Failed
    4 months ago
    Total: 38s
    #268175
  • πŸ‡ΊπŸ‡ΈUnited States phenaproxima Massachusetts

    I took a brief look at the branch, and the work in there looks pretty promising, but I want to just mention one thing that should be changed sooner rather than later, because it will block commit: the installer should not be changed at all. Configuring API keys for the AI providers will have to be done after installation, maybe as a link on the welcome dashboard.

    The installer is extremely opinionated and meant to be over as quick as possible. Any kind of post-install configuration, including setting API keys, has to be done after the fact.

    My suggestion would be to revert all changes to the installer, and then later (in a follow-up issue), add the user flow for configuring API keys post-install.

  • Pipeline finished with Success
    4 months ago
    Total: 439s
    #269375
  • Pipeline finished with Success
    4 months ago
    Total: 386s
    #269413
  • Pipeline finished with Failed
    4 months ago
    Total: 288s
    #269441
  • Pipeline finished with Success
    4 months ago
    Total: 477s
    #269576
  • πŸ‡©πŸ‡ͺGermany marcus_johansson

    @phenaproxima - Ah, sorry, I didn't see this until now. Got it, will revert and see how we can do a simple installation process post install.

  • Pipeline finished with Success
    4 months ago
    Total: 252s
    #271475
  • Pipeline finished with Failed
    4 months ago
    Total: 257s
    #271483
  • Pipeline finished with Failed
    3 months ago
    Total: 353s
    #284458
  • Pipeline finished with Failed
    3 months ago
    Total: 396s
    #284470
  • Pipeline finished with Failed
    about 2 months ago
    Total: 41s
    #323997
  • Pipeline finished with Failed
    about 2 months ago
    Total: 611s
    #323994
  • Status changed to Closed: duplicate 13 days ago
  • πŸ‡¦πŸ‡ΊAustralia pameeela
Production build 0.71.5 2024