Review all AI UX meeting notes for future items and create issues
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3559136. -->
Reported by: [kristen pol](https://www.drupal.org/user/8389)
>>>
<p>[Tracker]<br>
<strong>Update Summary: </strong>Review all AI UX meeting notes for future items and create issues<br>
<strong>Short Description: </strong>Review all AI UX meeting notes for future items and create issues<br>
<strong>Check-in Date: </strong>MM/DD/YYYY<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>We have been running a UX meeting for many months. Aidan started creating nice notes for these a couple/few months ago which are added to the meeting issues. There are topics in there that are for the future that will be lost if not captured in their own issues.</p>
<p>Closed UX meeting issues: <a href="https://www.drupal.org/project/issues/search/ai_initiative?text=ai+ux+meeting&assigned=&submitted=kristen+pol&project_issue_followers=&status%5B%5D=Closed&issue_tags_op=%3D&issue_tags=">https://www.drupal.org/project/issues/search/ai_initiative?text=ai+ux+meeting&assigned=&submitted=kristen+pol&project_issue_followers=&status%5B%5D=Closed&issue_tags_op=%3D&issue_tags=</a></p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Review all ux meeting issues and create issues for future tasks and topics to revisit.</p>
<p>-- Updated by Aidan with issues in slack thread from July until Nov 19 --</p>
<h2 id="ux-review-request-labels-within-automators">UX review request: Labels within Automators</h2>
<p><a href="https://drupal.slack.com/archives/CDL2YPBNX/p1751999970621279?thread_ts=1751998649.826909&channel=CDL2YPBNX&message_ts=1751999970.621279">https://drupal.slack.com/archives/CDL2YPBNX/p1751999970621279?thread_ts=1751998649.826909&channel=CDL2YPBNX&message_ts=1751999970.621279</a></p>
<h2 id="ux-review-request-automated-component-creator">UX review request: Automated Component Creator</h2>
<p><a href="https://www.drupal.org/project/experience_builder/issues/3532296">https://www.drupal.org/project/experience_builder/issues/3532296</a></p>
<h2 id="chat-ux-idea-this-page-context-thread-history-undo-like-cursor-s-ui-">Chat UX Idea: "This page" context / Thread History / Undo (Like Cursor's UI)</h2>
<p>Video of Cursor's approach for reference (@ symbol starts a type-ahead, also has a history of chat threads)</p>
<ul>
<li><a href="https://www.drupal.org/project/ai/issues/3542117">https://www.drupal.org/project/ai/issues/3542117</a></li>
</ul>
<h2 id="chat-ux-idea-show-tool-calls-in-the-chat">Chat UX Idea: Show Tool calls in the chat</h2>
<p>Both of these would be very helpful for Tool calling and persisting artifacts in threads(ie. a prompt like "Update the title on the current page to 'foo' and publish the page." would display the following tools: "Load current page entity" -> "Set title to foo" -> "Set node to published" -> "Save node").. It would also help in long running chats where you are iterating, tweaking, previewing, approving, etc before actually saving the thing you are doing.</p>
<p>Details in slack:</p>
<p><a href="https://drupal.slack.com/archives/C08QK2N7PMM/p1755101140854059">https://drupal.slack.com/archives/C08QK2N7PMM/p1755101140854059</a></p>
<p><a href="https://drupal.slack.com/archives/C08QK2N7PMM/p1757953710649459">https://drupal.slack.com/archives/C08QK2N7PMM/p1757953710649459</a></p>
<h2 id="meta-issue-of-chat-ux-ideas">Meta issue of Chat UX ideas</h2>
<p><a href="https://www.drupal.org/project/ai_initiative/issues/3544476">https://www.drupal.org/project/ai_initiative/issues/3544476</a></p>
<p>(Bundle the other two here)</p>
<h2 id="agent-ui-improvements-tool-api-agent-ui-">Agent UI Improvements (Tool API / Agent UI)</h2>
<p>Dev tools UI need UX / UI improvements</p>
<p><a href="https://www.drupal.org/project/ai_agents/issues/3552047">https://www.drupal.org/project/ai_agents/issues/3552047</a></p>
<p><a href="https://www.drupal.org/project/ai/issues/3552140">https://www.drupal.org/project/ai/issues/3552140</a></p>
<p><strong>Agent Tools Configuration UI</strong></p>
<ul>
<li>
<p>Tool and Agent UI needs 25+ tools to be added to agents/workflows</p>
</li>
<li>
<p>Major challenge: Users need to configure tools per use case per agent</p>
</li>
</ul>
<p><strong>Configuration issues:</strong></p>
<ul>
<li>Need to filter and select tools (potentially selecting many like Gmail does)</li>
<li>Bulk selection/management capability needed</li>
<li>
<p>Similar to module Views Bulk Operations or Filter enable/disable pattern but more complex</p>
</li>
<li>
<p>Need taxonomy/categorization system for tools:</p>
</li>
<li>
<p>By module?</p>
</li>
<li>
<p>By security level?</p>
</li>
<li>
<p>Other filters TBD</p>
</li>
</ul>
<h2 id="-identifies-critical-risk-in-journey-1-getting-ai-installed-"><strong>Identifies critical risk in Journey 1 (Getting AI installed) :</strong></h2>
<p><em>Assumption: People will want to do the canvas AI tasks similar to what's in the Driesnote.</em></p>
<ul>
<li>Most Drupal AI testing uses openAI (it's the default providers).
<ul>
<li><strong>BLOCKER:</strong> This requires a Tier 4 OpenAI API Key ($250 USD + Account is 14 days old)</li>
</ul>
</li>
<li>When you install AI we need to assume some knowledge but what should we be targeting?
<ul>
<li><strong>ASSUMPTION:</strong> Assume very little. Later we might setup something to ask, but for now we need something that "just works" with little knowledge</li>
</ul>
</li>
<li><strong>Potential Solution:</strong> Use <a href="https://openrouter.ai/">https://openrouter.ai</a> or similar
<ul>
<li>$11 USD or more bypasses the rate limit of OpenAI for new accounts so offers a much entry lower cost.</li>
<li>Also has "fallback" routes that automatically kick in (GPT5 fails, then Azure GPT-5 takes over)</li>
<li>Allows many popular models we might want to use by default instead of just openAI ones. (Claude or others)</li>
<li>Costs around +5-10% more for tokens</li>
<li>We have a module for it already (<a href="https://www.drupal.org/project/ai_provider_openrouter">https://www.drupal.org/project/ai_provider_openrouter</a>)</li>
</ul>
</li>
</ul>
<p>NOTE: Christoph mentioned that some providers may sponsor setup (Google?) with free tokens usage this might </p>
<h2 id="discussion-related-to-openai-sdk-allowing-easier-installation-only-need-to-config-yaml-">Discussion related to OpenAI SDK, allowing easier installation (only need to config YAML)</h2>
<p>If OpenAISDK is included in AI module, we can add providers without needed to install modules (if they are OpenAI compatible). </p>
<p>What should the UI look like (Aidan did a quick mockup)?</p>
<p><a href="https://drupal.slack.com/archives/C08QK2N7PMM/p1762791761879079">https://drupal.slack.com/archives/C08QK2N7PMM/p1762791761879079</a> << Screenshot in thread</p>
<h2 id="ux-review-request-what-should-we-name-the-chat-consumer-executor-">UX review request: What should we name the "Chat consumer/executor" ?</h2>
<p><a href="https://drupal.slack.com/archives/C0803LX4536/p1762945706950149?thread_ts=1761136716.827719&cid=C0803LX4536">https://drupal.slack.com/archives/C0803LX4536/p1762945706950149?thread_ts=1761136716.827719&cid=C0803LX4536</a></p>
<h2 id="how-do-we-filter-the-dashboard-to-high-quality-ai-recipes-modules-">How do we filter the Dashboard to high-quality AI recipes / Modules?</h2>
<ul>
<li>How can recipes technically define and signal their specific model/modality requirements (e.g., "requires a model that supports vision" or "tested with GPT-4.1")?</li>
<li>How will the "Features" (recipes) and "Extensions" (modules) lists be filtered to show only AI-relevant items, and what changes might be needed in Project Browser to support this?</li>
</ul>
<p>[Plan] Propose a curation mechanism for "AI Official" modules and recipes<br>
<a href="https://www.drupal.org/project/ai_initiative/issues/3558927">https://www.drupal.org/project/ai_initiative/issues/3558927</a></p>
<p>NOTE: It's a comment here but we'll need a different issue for "Tested on Claude 4.5" "GPT-4.1 Recommended" labels which will probably need a different issue.</p>
issue