>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3561258. --> Reported by: [yautja_cetanu](https://www.drupal.org/user/626050) >>> <p>[Tracker]<br> <strong>Update Summary: </strong>[One-line status update for stakeholders]<br> <strong>Short Description: </strong> Use the Workspaces module to allow multiple people to collaobrate on a live Drupal site with git-style tracking of Content and Config. This includes revisions, branching revisions and even merging and managing conflicts for non developers. AI Agents can just become another user making use of all of this.<br> <strong>Check-in Date: </strong>MM/DD/YYYY<br> <strong>Additional Collaborators: </strong><br> <em>Metadata is used by the <a href="https://www.drupalstarforge.ai/" title="AI Tracker">AI Tracker.</a> Docs and additional fields <a href="https://www.drupalstarforge.ai/ai-dashboard/docs" title="AI Issue Tracker Documentation">here</a>.</em><br> [/Tracker]</p> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>There are many ways AI Agents can make changes to a Drupal site both through the Drupal CMS AI Agents but also via claude code etc. However, everything requires a developer in the wild. Claude Code needs developers to check the code but even Drupal CMS AI Agents are unlikely to be used on live sites that frequently don't allow end-users and site builders to work on it. Many organisations find moving things from Test to live a long process however much we improve the tooling.</p> <p>So what if we could safetly make changes to the live Drupal site, no developers were ever needed to approve things because the changes were safely within a workspace and they could handle merging things. If we can make the whole process and UX work well for humans managing other humans this can be powerful at managing large swarms of AI Agents making changes across the site.</p> <p>This also helps improve the trustworthiness of AI Agents.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>(I'm new to workspaces, so many of the things below will likely exist in issues somewhere).<br> This issue is inspired by: <a href="https://dri.es/how-ai-could-reshape-cms-platforms">https://dri.es/how-ai-could-reshape-cms-platforms</a></p> <p><strong>Workspaces for Content</strong></p> <ul> <li> Create Tools for AI Agents to make use of Workspaces for content, so they open things in a new workspace.</li> <li> Perhaps create Drupal CMS content editing agents that make use of these workspaces.</li> <li> Handle branching of collections of content so multiple groups can work on different approaches to changes to main.</li> <li> Handle conflict resolution across or fields in a manner usable to end-users.</li> <li> Have AI make use of the conflict resolution so it can propose resolutions.</li> <li> Handle permissions so multiple groups can handle changes in the workspace including different groups of AI Agents.</li> <li> Agent changes can make their own workspaces, they can make their own branches off the workspaces or be added to make direct changes to a workspace.</li> <li> When an end-user makes a change in the Chatbot, if workspaces are used this needs to be clearly changed in the UI.</li> </ul> <p><strong>Workspaces for Config</strong><br> <a href="https://www.drupal.org/project/wse">https://www.drupal.org/project/wse</a><br> High level issue for exploring different approaching to handling the branching of config and content given the limitations of a database.</p> <ul> <li><span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ai_initiative/-/work_items/3561263" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ai_initiative/-/work_items/3561263</a></span></li> </ul> <p><strong>Real-time Collaborative editing</strong></p> <p>Could explore this: <a href="https://www.drupal.org/project/edit_mesh">https://www.drupal.org/project/edit_mesh</a> </p> <ul> <li>PoC of what a "Google Doc" experience in Drupal could look like.</li> <li>Allow others to safely make edits to the page you are looking at in real time.</li> <li>See where others have their cursor.</li> <li>Allow specific "Suggestions" vs edits.</li> <li>See who is looking at the page and click to visit.</li> <li>Allow people to have comments directly on the page.</li> <li>Allow AI Agents to add content via a similar approach to manage their changes.</li> <li>Make sure this works effectively with workspaces. </li> </ul> <h3 id="summary-remaining-tasks">Target date or deadline</h3> <h3 id="summary-remaining-tasks">Remaining tasks</h3> > Related issue: [Issue #3560637](https://www.drupal.org/node/3560637)