Drupal AI UX meeting 20 April 2026
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3565733. -->
Reported by: [kristen pol](https://www.drupal.org/user/8389)
>>>
TYPE html>
<div><p><br>
<br>
</p><head></head><br>
<meta charset="UTF-8"><br>
<title>UX Meeting Notes — Monday, April 20, 2026</title><br>
<br>
<body>
<h2>Meeting Overview</h2>
<p><strong>Date:</strong> Monday, April 20, 2026<br><br>
<strong>Attendees:</strong> Aidan, Bruno, Arian, Emma, Marcus, Darren, Salim, Ángela</p>
<h2>Default Tools Form Editor — <a href="https://www.drupal.org/node/3577937">#3577937</a></h2>
<ul>
<li>Marcus clarified Label and Description are read by the LLM at invocation, not admin-only copy, so wording affects agent tool-selection behavior.</li>
<li>Parameter values accept Drupal tokens (e.g. entity_id); the UI needs help text and examples so agents can forward already-loaded context instead of re-fetching.</li>
<li>Pre-populate parameter suggestions from the plugin definition and surface per-parameter descriptions as info-icon tooltips; the data already exists in the AI API Explorer.</li>
<li>Rename the "default information tools" label (Marcus called it the stupidest name, pattern borrowed from Crew AI) and rename "Description" toward "Expected tool output"; Emma's point that "expected" carries the right uncertainty held.</li>
<li>Label stays required, Description becomes optional and turns into a textarea; add explanatory help text clarifying the LLM sees only label, description, and tool output, and an optional preview button when AI API Explorer is installed.</li>
</ul>
<h2>Provider Notifications — <a href="https://www.drupal.org/node/3575689">#3575689</a></h2>
<ul>
<li>Aidan and Emma concluded between meetings that the "new recommended model" notification targets the wrong user; marketers do not swap base LLMs and developers already know when they update a module.</li>
<li>Drop the recommended-model badge from the default provider settings page entirely; partial reversal of the April 13 direction.</li>
<li>Keep the full deprecation treatment: badge for any non-null deprecation date, deprecation date injected into the select-list item label, AI dashboard system message for models within two months of end-of-life.</li>
<li>The "recommended / tested" concept moves to the agent or recipe level, grounded in AI Eval runs that already exist; Chicago demo is the live example because it specifically needs Claude Opus.</li>
<li>A new meta-issue will carry recommended-at-agent-level forward; open question remains whether a lightweight "default model" indicator belongs inside the provider select dropdown.</li>
</ul>
<h2>Chatbot UX Evolution — <a href="https://www.drupal.org/node/3544476">#3544476</a></h2>
<ul>
<li>Marcus kicked off a front-end research spike on extending deep-chat; library decision waits on the result.</li>
</ul>
<h2>Chicago Prototype on Drupal Forge</h2>
<ul>
<li>Install past composer and profile errors; two-key requirement is the remaining UX blocker.</li>
<li>Drupal Forge to cover embeddings via LiteLLM, reducing the demo to one user-supplied Claude key.</li>
<li>Salim and Darren coordinating demo keys and user key-swap flow offline.</li>
</ul>
<h2>Front-End Resource Pool and AI Review UX Session</h2>
<ul>
<li>Two or three front-end contributors have open capacity; Arian collecting expertise details, AI Review likely destination.</li>
<li>One-hour AI Review UX sketching session this week with Aidan, Bruno, Ángela, Emma; Christoph's architecture session runs separately later.</li>
</ul>
<h2>Decisions</h2>
<ul>
<li>"Recommended model" belongs at the agent or recipe level, not on default provider settings.</li>
<li>A new meta-issue will cover "recommended / tested models at the agent or recipe level".</li>
</ul>
<h2>Questions</h2>
<ul>
<li>Final phrasing for the renamed "Description" field and the "default information tools" label.</li>
<li>Whether to show a lightweight "default model" indicator inside the provider select dropdown.</li>
</ul>
<h2>Next Steps</h2>
<ul>
<li><strong>Bruno:</strong> Iterate <a href="https://www.drupal.org/node/3577937">#3577937</a> and <a href="https://www.drupal.org/node/3575689">#3575689</a> per the decisions above.</li>
<li><strong>Aidan:</strong> Open a new meta-issue for recommended/tested models at the agent or recipe level.</li>
<li><strong>Aidan/Bruno/Ángela/Emma:</strong> Schedule the AI Review UX sketching session Mon afternoon or Tue.</li>
<li><strong>Salim/Darren:</strong> Coordinate Drupal Forge demo keys and user key-swap flow.</li>
<li><strong>Marcus:</strong> Run the deep-chat extension research spike and report back.</li>
</ul>
<p></p></body><br>
> Related issue: [Issue #3565732](https://www.drupal.org/node/3565732)
issue