>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3565723. --> Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> <h1 id="ai-ux-meeting-summary-february-16-2026">AI UX Meeting Summary &mdash; February 16, 2026</h1> <p><strong>Attendees:</strong> Aidan Foster, Bruno, &Aacute;ngela Salda&ntilde;a Contreras, Arian Raeesi, Marcus Johansson</p> <hr> <h2 id="topics">Topics</h2> <h3 id="markdown-editor-in-context-control-center">Markdown Editor in Context Control Center</h3> <ul> <li>MDX editor MR for CCC was merged over the weekend by Kristen.</li> <li>Tokens (Drupal tokens) are the replacement mechanism for CCC. Variables (Twig autocomplete) are available in AI Core 1.3 dev as "advanced mode" but not yet implemented in CCC.</li> </ul> <h3 id="ai-core-shared-ui-library-ccc-refactoring">AI Core Shared UI Library &rarr; CCC Refactoring</h3> <ul> <li>Pulled the CSS refactoring ticket into the current sprint to avoid a full sprint delay before DrupalCon. Bruno will work on it Tue/Wed; Eric Homanchuk (back from vacation) is fallback.</li> <li>Work is CSS-only, no update hook needed, can go into Friday's release candidate. Aidan needs to communicate to reviewers why new CSS is being added that isn't yet consumed.</li> <li><strong>Decision:</strong> Pull CCC UI library refactoring into current sprint.</li> </ul> <h3 id="ux-ticket-tagging-sprint-process">UX Ticket Tagging &amp; Sprint Process</h3> <ul> <li>CCC sprint issues should come through Kristen, who decides production vs. innovation classification. Additional UX tags on sprint issues are fine and won't conflict.</li> <li>Aidan will manually track adding/removing UX-motivated issues to/from sprints and communicate changes to Kristen.</li> </ul> <h3 id="tool-call-visibility-design-angela-s-exploration-">Tool Call Visibility Design (Angela's Exploration)</h3> <ul> <li>Angela presented three Figma versions. Team decided: <strong>checkmarks as default icon</strong> (tools/agents can optionally define custom SVGs), <strong>no timeline connector line</strong> (saves vertical space in docked panel), and <strong>planning/execution steps should look the same</strong> to users.</li> <li>Still needed: collapsed/non-expanded state design, and one more version showing a text-generation workflow. Artifacts are out of scope &mdash; no known use case for rendering executables in Drupal's chat UI.</li> <li><strong>Decision:</strong> Checkmarks as default, no timeline line, planning and execution look the same. No artifact rendering in chat UI for now.</li> </ul> <h3 id="chat-to-content-workflow-drupalcon-test-scenarios">Chat-to-Content Workflow &amp; DrupalCon Test Scenarios</h3> <ul> <li>Aidan is drafting test cases for QED42 covering: well-crafted prompts that just build the page, vague prompts that trigger clarifying questions, mismatched content/intent detection, and multi-turn page refinement.</li> <li>Marcus will share content recipe export commands for reproducible demo content. Key lesson from Vienna: <strong>lock the theme version</strong> to prevent component changes from breaking demos.</li> <li><strong>Decision:</strong> Lock theme version for DrupalCon demo content.</li> </ul> <h3 id="deep-chat-future-chat-ui">Deep Chat &amp; Future Chat UI</h3> <ul> <li>Deep Chat stays through 2.0. Marcus requested thinking/tool call thread support upstream; maintainer declined. A "chat consumer" abstraction in 2.0 will make future swaps easier.</li> <li><strong>Assistance UI</strong> identified as a potential replacement for complex full-screen workflows (threads, reasoning, planning all built in).</li> <li><strong>Decision:</strong> Keep Deep Chat through 2.0; work within its constraints.</li> </ul> <h3 id="tool-call-overflow">Tool Call Overflow</h3> <ul> <li>For cases with many tool calls (e.g., 50 taxonomy terms), ship as-is under the collapsed expander. Revisit after testing real scenarios.</li> <li>Future improvement: summarized counts ("created 50 terms") instead of listing each one, plus max-height with nested expander.</li> <li><strong>Decision:</strong> Ship as-is, iterate later.</li> </ul> <hr> <h2 id="questions">Questions</h2> <ul> <li>How should tool call summaries work when there are 50+ calls? (Deferred &mdash; test first, design later)</li> <li>What's the right UX for a "chat consumer" abstraction? (Naming TBD &mdash; acknowledged but deferred)</li> </ul> <h2 id="next-steps">Next Steps</h2> <ul> <li><strong>Bruno:</strong> Work on CCC UI library CSS refactoring Tue/Wed; post progress updates in #ai-ux Slack. If incomplete, hand over to Eric.</li> <li><strong>Angela:</strong> Add collapsed state to tool call designs; create text-generation workflow version; wrap up designs this sprint.</li> <li><strong>Aidan:</strong> Communicate UI library rationale to reviewers; manage UX sprint tag tracking with Kristen; work on chat-to-content test scenarios.</li> <li><strong>Marcus:</strong> Share content recipe export commands with Aidan; continue Canvas AI edit tool review.</li> <li><strong>Arian:</strong> Continue sprint coordination; track UX tag additions.</li> </ul> > Related issue: [Issue #3565721](https://www.drupal.org/node/3565721)