Tag AI Automator LLM requests

Created an MR doing what's proposed above so the idea & the code can be reviewed

$prompt and $instance aren't used here - should we remove them from the signature, or are we expecting extending classes to override and make use of them?

I'm not sure. I can't think of any cases where $prompt could be useful but I can imagine circumstances where $instance might (if there's a specific provider/model for a task and tagging something about the instance could be useful)?

I wonder if bundle would be worth adding?

That makes sense, I'll update the MR shortly

I'm not sure. I can't think of any cases where $prompt could be useful but I can imagine circumstances where $instance might (if there's a specific provider/model for a task and tagging something about the instance could be useful)?

Regarding $instance, the model gets automatically tagged, but there could for sure be combinations where it used. Also specific types of a interfaces have specific methods that might be interesting to tag - for instance the voice id on text-to-speech. Prompt in certain use cases, like SERP API, just means search word, so there might be a use case.

I know from when I was using AI Interpolator, I didn't set parameters that was perhaps usable for any plugin extending it. So I think its good too keep both.

Updated with the bundle tag but I've left all the parameters. As Marcus suggests, it's better to provide too much info for future implementations than not enough.

marcus_johansson → credited andrewbelcher → .

Not sure how to manage issues for backports but I've created a 1.0.x backport MR for this: https://git.drupalcode.org/project/ai/-/merge_requests/533

justanothermark → closed merge request !533