[Meta] Features to focus on for v1.1

Created on 3 December 2024, 3 months ago

Problem/Motivation

We had a number of planned features for v1.0 but they arn't strictly necessary for v1.0, just would be nice to make things feel feature complete. As a result I'm pulling them out of Road to rc1 and v1.0 and putting things here that arn't absolutely necessary for v1.0.

More and more people are wanting to use the AI module and its parts in production that I think we should try and get a v1 that we truly support.

This is a follow-up to 🌱 [Meta] Path to rc1 Active

Remaining tasks

Assistants + Chatbot:

  • Ability to Store chat history in the DB
  • Need to make sure history is inline with Drupal's approach to obtaining consent
  • Allow for multiple threads and ability to select different threads.
  • Move the Chatbot to a proper Javascript framework such as React
  • Allow the chatbot to control things outside of the page such as move the browser to a div, refresh the page / redirect you or highlight a div.
  • Potentially understand how Agents interact with the messages by exploring other frameworks such as https://github.com/openai/swarm or https://ai.pydantic.dev/#hello-world-example. Maybe Assistant should be tied more closely to agents?

Our current thinking is that there are good reasons that Assistants are a fundamentally different abstraction to agents. Agents can mostly exist in Code or interact with a variety of user interfaces such as minikanban, a standard create drupal form. Whereas Assistants are tied fundamentally to the Chatbot UI. They have things like storying a history in the DB, selecting different threads. Maybe advanced UIs such as mocking up designs in the chatbot where it expands if you hover over it.

API changes

Data model changes

🌱 Plan
Status

Active

Version

1.0

Component

AI Core module

Created by

🇬🇧United Kingdom yautja_cetanu

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

Comments & Activities

  • Issue created by @yautja_cetanu
  • 🇬🇧United Kingdom yautja_cetanu

    https://www.drupal.org/project/ai/issues/3485449#comment-15884039 🌱 [Meta] Bring AI Search, Assistants and Chatbot out of Experimental Active - This comment has some details about the "Lexical vs semantic search stuff"

  • 🇬🇧United Kingdom seogow

    Crossed out feature requests were implemented/present in 1.0.x, commit 7809b7fd392ab3eef2c361437091aa91913a334e.

    • - this is possible with existing module. It depends on VDB implementation (and capabilities).
    • - the existing code does this.
    • Views filters - working with RAG - Does work, but not good yet. - Probably need a specific Vector Exposed filter - this has to be done case by case, but we should/could probably start with disabling Views filters which actually do not work with VDB Search API index.
    • Have the search respect user permissions. (permissions in Drupal is so huge computationally - So Drupal even does recalculation by itself). - This can be actually done using the same method as Drupal does, @yautja_cetanu it might be worth opening a new ticket.
  • 🇬🇧United Kingdom scott_euser

    Yeah definitely the filtering is vbd provider specific. Filters are definitely not as extensive as the options in Views itself, and contrib extends those options further. I can't see a realistic path to maintaining filter feature parity hence the boost plugins for SOLR/database essentially working around the problem

  • 🇬🇧United Kingdom scott_euser

    (until postgres/mariadb/solr actually have sufficient performance and support I guess - something I haven't been keeping up to date with)

Production build 0.71.5 2024