Currently we have some helper plugin actions that lets you:
This makes it possible to setup something from scratch very easily. The issue with that is that there would be a lot of recipes that would either require some base recipe or would need you to setup things that might already be setup.
It would instead be much easier if the recipe could do a simple check if the operation type it is looking for has a provider installed or if the operation type it is looking for has a default model setup.
So it could look something like this:
config:
actions:
custom_config:
verifyAiDefaults:
providers:
- chat_with_tools
default_model:
- chat_with_tools
This is a work around that uses config actions in a way its not meant to be used - for validation of requirements before application, but since any exception rolls back the configuration, it would work.
Active
1.2
AI Core module
I also added some new documentation for all things recipes and AI module.
I have discussed this with @thejimbirch and @phenaproxima and there is not clear solution to this - this is obviously a workaround, so I will not merge this until we have a good solution in recipes/drupal core for this or they confirm that there will not be a solution for recipes.