- Issue created by @yautja_cetanu
- 🇬🇧United Kingdom yautja_cetanu
A couple of things from our initial investigations:
1. Workspaces looks good but doesn't support field config yet which is essential so its unlikely to be ready for RC1
Below is an AI Agent trying to add something to a vocab.
It shows up as not yet pushed.
2. We have verbose responses with links and details.
Here it is medium levels of verbosity. It tells you the category but it doesn't tell you literally every term its going to make. It does give you links to places where you can check the work.
Below is a details dropdown. It shows to a log of the actual things Drupal has done and this log is generated by code, not by an LLM and therefore will be completely accurate. However its what Drupal needs to know, it doesn't necessarily make sense to an end-user. We can at least improve it by making it so the labels are printed. But it will still be fairly techy.
- 🇩🇪Germany marcus_johansson
First of all the Workspaces modules + WSE Config is really cool, however I did get stuck on most config entities where it currently won’t let me save them into a Workspace, which is how things are supposed to work as far as I could see. With Views it works.
I could have the chatbot switch over to its own workspaces anytime it takes an action and currently I had to manually publish the Workflow But it’s some work to get something useful there both from our side and on, I’m guessing, the WSE’s side.
In the Agent Interface we have added so that you can fetch all the content and config creations and changes as ids, this was not meant for the Chatbot UI from the beginning, but we have added a detail under the chat answer that can be toggled in the chatbot settings where you can see the actual changes made by the last response from the chatbot.
What has also been added, so far in the taxonomy and fields agent, is that they will return links for every part of the system they change. This means that the Chatbot can be prompted to return this, which I have updated it to do on the Drupal CMS MR. So any beginner to Drupal would find links in the response where they can verify and see where changes are made.
See screenshot below for example of both changes:
Currently the agents are hardcoded not to do any deletions, the question is if we should also extend this to editing of configs that have substantial (10+) content items connected to them? This would make sure that you have a tool that can help you with the initial building, but that can’t really do any changes that are not revertable without a database backup/Workspaces?
- 🇬🇧United Kingdom yautja_cetanu
- We should have more details in the details. So if we're changing the name from X to Y it should say that. If its doing taxonomy terms it should show the term itself, not just the ID
- 🇩🇪Germany marcus_johansson
From the fixed tickets and fixed structure on how to add original vs changed config and content.
Diff on config entities:
Labels on content entities:
Later I will see if I can force this via interface, so anyone doing agents has to follow this. It would also help with fixing of revert of the last run agent(s)