Given that this will be using AI Agents to do things. It could be in Drupal instead of Drush and use AI Drush agents to do things instead.
Duplicate of 📌 Simple approach to bringing advanced metadata into Canvas AI Active
Duplicate of 📌 Simple approach to bringing advanced metadata into Canvas AI Active
I don't have much to add other than that this looks good to me
So the argument for it is
- having openai SDK required by core shouldn't impact anyone using Gemini as they will just ignore it.
- from a UI point of view with my proposal above the end user and even admin will not see or know anything about the openai stuff.
- so few people just use Gemini that I don't think we should focus the UX and DX on the few. This attitude has made the AI module so difficult for everyone else trying to just get started.
- almost all new providers are taking the approach of the openai SDK. Litellm, amazee AI, EC gpt,olama, open router, obviously openai, fireworks AI.
- many organisations are starting to use a router like litellm to connect to Gemini etc anyway
It would allow for a significantly improved experience for the majority of people
https://www.drupal.org/project/ai/issues/3551928 ✨ Submodule to get people started with ai module ai_kickstart Active - Be good if they could start with this
Possibly tabs could work:
- The "Simple View" should be what most people see and it should only have a small collection of relevant tools not everything so I don't think it will grow too much.
- If it does grow a kind of tool library like the media library with filters and search might be better.
- Using Visual flow editors like flowDrop and ECA might be just better for the complex tools anyway.
- The problem with tabs is switching between them isn't great, so if its a task that involves lots of back and fourth, I don't think tabs will work. I think Agents do involve back and forth.
https://www.drupal.org/project/ai/issues/3552690 📌 Create an AI module Setup guide and checklist Active - I think maybe this approach Frederick will commit could go here too?
Looks good. I wonder if there should be a toggle. Simple tools by default and then you can click a button and see all the base tools?
We could also have it tied to permissions.
I think field set shouldn't appear as a tool for most people.
Perhaps next to Status for each test.
Even better would be a kind of Gantt chart log thing where you can see visually the relative times it takes! But that might be a bit advanced.
Something like: https://claude.ai/public/artifacts/58a06f78-2552-40fc-add8-0eb17f483a02
OR: https://claude.ai/public/artifacts/dd00223a-017f-47c6-9ceb-6c29e741d879
But I think this is a follow-up issue. For now, I think having the time it took for each test specifically next to status would be good.
- Things are busy before Vienna but owuld be good to have some onboarding meetings with them and details in the Sponsors tracker.
We have one with the CCC, we can improve things but one exists.
It works, we can improve things but the fundamentals work
Follow up issue here: ✨ Add a planning tool for plan-and-execute vs react Active
yautja_cetanu → created an issue.
yautja_cetanu → created an issue.
yautja_cetanu → created an issue.
--- AI TRACKER METADATA ---
Update Summary: Allows us to pull a wider variety of images than is in the media library which is great for demos and likely good in production for one-off pages. Code is in a module and github, haven't figured out "proper" integration with Canvas AI
Check-in Date: MM/DD/YYYY (US format) [When we should see progress/get an update]
Due Date: MM/DD/YYYY (US format) [When the issue should be fully completed]
Blocked by: [#XXXXXX] (New issues on new lines)
Additional Collaborators: @username1, @username2
AI Tracker found here: https://www.drupalstarforge.ai/
--- END METADATA ---
yautja_cetanu → created an issue.
yautja_cetanu → created an issue.
yautja_cetanu → created an issue.
yautja_cetanu → created an issue.
yautja_cetanu → created an issue.
Implement New Tracker Metadata Template (Both should work)
[Tracker]
<strong>Short Description: </strong> [One-line issue summary for stakeholders]
<strong>Update Summary: </strong> [One-line status update for stakeholders]
<strong>Check-in Date: </strong>MM/DD/YYYY
<strong>Due Date:</strong> MM/DD/YYYY
<strong>Blocked by:</strong> [#XXXXXX] (New issues on new lines)
<strong>Additional Collaborators:</strong> @username1, @username2
AI Tracker found here: <a href="https://www.drupalstarforge.ai/" title="AI Tracker">https://www.drupalstarforge.ai/</a> and docs on how to use the metadata above can be found <a href="https://www.drupalstarforge.ai/ai-dashboard/docs" title="AI Issue Tracker Documentation">here</a>.
[/Tracker]
yautja_cetanu → created an issue.
yautja_cetanu → created an issue.
Added tags for tracking purposes
Happy with this but note everything else we've ended up with lower case.
strategic evolution
priority
beta blocker
So should we do all the above lower case?
workstream 1a
ai views
yautja_cetanu → created an issue.
Given the comment here: https://www.drupal.org/project/ai/issues/3485449#comment-16267002 🌱 [Meta] Bring AI Search, Assistants and Chatbot out of Experimental Active - that suggests we will not be taking AI Search out of experimental until 2.0 due to a number of refactors I think this isn't a beta blocker for 1.2.
As per this issue, I do not think this issue is a blocker to taking AI Search out of experimental buti a nice to have. There are plenty of work arounds and this is a fairly niche, as long as we have good errors I do not think this should block taking it out of experimental and certainly not 1.2