Create Base Tools

The kicker standout with such a tool will be the Views base tool - no other CMS, CMS, framework or AI workflow runner will have anything close to it in case of adaptability, security and flexibility.

So here are four examples of what this should/could solve:

Rag Search

Everytime someone adds a RAG index, it will automatically create a tool for that index with a default value of finding 10 items over 0.3 min score with entity permissions enabled.

But you should also be able to setup versions of this where you:

• pick the index (required)
• pick how many items to choose (optional - LLM will pick otherwise)
• pick the min score (optional - LLM will pick otherwise)
• turn of entity permissions (optional - will be on by default, with clear description when it makes sense to turn it off for performance reasons)

Entity Creation/Update

This should probably not be generated automatically, but need a active decision, where you:

• pick the entity type (required)
• pick the bundle (required if bundelable)
• pick the operations create and/or edit (required)
• pick the fields (required, but has to show required fields, on create)

This means that you can create an entity publisher, or an entity change one specific flag tool, but also a full entity creation tool.

Plugin Definitions

This should not be generated automatically, but needs an active decision, where you:

• pick the plugin manager (required)
• pick the permissions (required) - this might need flexibility to say for instance, that any "Change fields on entity type X" is approved
• pick the attributes to show (required)
• pick the output method like csv, yaml (required)

Flush the cache(s)

This should not be generated automatically, but needs an active decision, where you:

• pick the cache buckets or all (required)
• pick the permissions (required)

I think the important thing with entities is that it should be very obvious when you create a new content type and bundle that you can make a tool for it with a permission. Something like

- Create an AI Tool for Agents to interact with this entity.

@yautja_cetanu - yup, but I think for 1.2.0 we should ship the functionailty with a plain form and in 1.3.0 fix the UX/UI for it?

Otherwise it will take a long time to get a release out, and having the possibility for more advanced developers to already start shipping tools rather soon, would be nice.

We are doing some issue management housekeeping and adding/removing components.

We are removing the "Code" component and want people to categorize issues with the best module/submodule component.

Moving this issue to "...to be triaged" to decide on priority, etc.

See 📌 Update AI module project components Active for more details.