Roughly three months have passed since AI 1.1.0 was released and we are getting ready for the next step in the history of Drupal AI.
This means that we will have an upgrade path before the next RC release, all major features are developed and any known security or critical bug is fixed. As a developer you can trust that the API’s are set.
One important upgrade path is that we are moving out the AI ECA module, to https://www.drupal.org/project/ai_integration_eca so that can develop in a more rapid tempo then the release cycles of the AI module.
As a developer you can trust that the API’s are set.
If nothing unexpected happens, the plan is to have a RC 30th of September and a production release 7th of October.
What does it bring?
The feature list of changes since the 1.1.0 release of the AI and AI Agents is too long to list and a lot has been written already in the alpha releases. But it includes:
Field Widget Actions
The field widget actions module lets you place as many buttons as you like on any form element for fields in Drupal to trigger AI Agents, AI Automators, ECA workflows or you custom integrations.
This means that you can have buttons to pick categories based on specific criterias, have title suggestions and thousands of other solutions.
Prompt Library
With the release of 1.2.0, we make it possible to ship prompts as general reusable configurations and categorize them where they belong.
New Automator Types
In 1.2.0 you will be able to use the Automator to contextualize using Views, create alt texts, rewrite filenames and fill out the summary on the Text with Summary field.
Prompt Replay provider
For testing reasons we usually have the problem that we do not want to send requests to an expensive AI provider just to try a piece of code over and over. We have solved that by having a proxy provider that can record requests and then replay them over and over, including in functional and kernel tests.
Agent improvements
The agents are getting more controllable and usable, including being able to create artifacts to pass over, output structured schemas, controlling descriptions of tools, status polling services, getting recursive tool results, being able to be triggered in CKEditor and more.
New chatbot Assistant styling
Because the assistant is designed primarily for website editors and administrators, the chatbot should reflect that focus. Starting with version 1.2.0, a new default styling will be introduced that integrates more seamlessly with the overall CMS design. The current style are still available of course.
Please try it out!
Whilst we wouldn’t recommend deploying to production systems yet, you can definitely start developing with the new features and try them out.
We are eager for any feedback!