andrewbelcher → created an issue.
Oh, and I also added the ability to apply restrictions via the tool explorer, in line with what can be configured on agents in AI Agents. That makes it a lot easier to test!
I believe that's all tests fixed - failure was a runner issue.
I've slightly tweaked it to not automatically modify the required property. That can still be done by things that modify the definition though.
I would actually describe this as a bug, and a have upped it to major as there is no reasonable workaround that I can see.
So to get the LLM to respect this, I had to put reiterate that it's a constant multiple times by:
- Setting
const - Setting
enumwith a single value - Adding a note to the description.
But it was consistently behaving after that!
I also adjusted the way required constraints are managed so it's computed at the point of render rather than adding the property, so it respects and changes. I've also made isRequired always FALSE if it's a constant.
andrewbelcher → created an issue.
Original issue in AI was a duplicate of 📌 Add module dependencies to tools Active which has been done!
Ah, just realised this is a duplicate of a ticket Marcus has already fixed - 📌 Add module dependencies to tools Active .
Steps given in the initial report.
The isAvailable method only appears to be called in ai_agents_extra's MCP plugin, and the ai_content_suggestions settings form.
That probably should be checked in other places, but is more suitable for "run time" checks, rather than dependency checks. For example, if a function call tried to inject a dependency from a module not enabled, you wouldn't be able to instantiate the plugin to call isAvailable.
marcus_johansson → credited andrewbelcher → .
andrewbelcher → created an issue.
PR also includes some fixes to type hints/usage etc.
andrewbelcher → created an issue.
andrewbelcher → created an issue.
andrewbelcher → created an issue.
andrewbelcher → created an issue.
andrewbelcher → created an issue.
andrewbelcher → created an issue.
andrewbelcher → created an issue.
andrewbelcher → created an issue.
andrewbelcher → created an issue.
andrewbelcher → created an issue.
andrewbelcher → made their first commit to this issue’s fork.
andrewbelcher → made their first commit to this issue’s fork.
I think this should actually be against the AI module. OpenAI provider (along with most other providers) do make use of key.
However AI, which is where the explicit dependency is, doesn't directly use it. In the case of the AWS Bedrock provider, key is never used as it makes use of the AWS module's profiles to manage the credentials.
marcus_johansson → credited andrewbelcher → .
andrewbelcher → created an issue.
andrewbelcher → created an issue.
PRs ready for both 1.0.x and 1.1.x.
andrewbelcher → created an issue.
Looks good now, thanks Marcus!
andrewbelcher → created an issue.
Initial prompt addition in MR, but I think we do need to look at the rest of the task, especially one shot learning examples.
andrewbelcher → created an issue.
andrewbelcher → created an issue.
andrewbelcher → created an issue.
andrewbelcher → created an issue.
andrewbelcher → created an issue.
Struggling to reproduce the error, but the PR looks good and should give safety against the error.
andrewbelcher → created an issue.
But how would I know how to do this as a site admin? During the process of installing drupal cms and going to install the ai recipe, I never see the place to manage my privacy settings.
The only way I knew to do this was by looking at the code. My privacy settings didn't appear on the admin pages, it didn't appear in my profile. I had to look quite hard to find it.
It looks like it might be related to how Klaro! handles whether consent for itself has been granted. When I manually open the Klaro! consent manager and save with the default settings:
Once that has been saved, a klaro cookie is set, and from that point on, the chat shows the Always option:
andrewbelcher → created an issue.
Can confirm this is the correct approach for 10.3 as well.
andrewbelcher → created an issue.
andrewbelcher → created an issue.
Still need to check D10 compatibility.
andrewbelcher → created an issue.
andrewbelcher → created an issue.
andrewbelcher → created an issue.
andrewbelcher → created an issue.