>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3565726. --> Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> <p><strong>Attendees:</strong> Aidan Foster, Emma Horrell, Bruno Carvalho, Jamie Abrahams, Kristen Pol</p> <p><strong>Note:</strong> Aidan is on vacation for the next two weeks. Emma will facilitate the March 9 and March 16 meetings.</p> <h3 id="tool-call-ui-design-3572362-resolved">Tool Call UI Design (#3572362) &mdash; Resolved</h3> <ul> <li>&Aacute;ngela's Figma designs were finalized and the issue was closed. Implementation has been assigned to QED42 as a sprint ticket. Check-in expected at the Tuesday meeting.</li> </ul> <h3 id="ai-agents-test-module-3541315-bruno-s-ux-improvements">AI Agents Test Module (#3541315) &mdash; Bruno's UX Improvements</h3> <ul> <li>Bruno demoed before/after screenshots showing significant UX cleanup: rainbow background colors replaced with shared UI library pills, View Results separated from Run Test/Edit actions, empty state guidance added, and module moved to configuration section.</li> <li>The MR received review comments, mostly about update hooks (likely unnecessary since the module is still alpha). A sub-issue was suggested for improving the individual test detail/review page, which still needs work.</li> </ul> <h3 id="ccc-context-list-ui-subcontext-scope">CCC Context List UI &mdash; Subcontext &amp; Scope</h3> <ul> <li>Bruno showed the new context list implementation using a list builder (replacing the views-based approach, which had configuration errors). The "+7" overflow pattern using tooltips was reviewed and approved as a good solution for displaying excess use cases.</li> <li>Decisions: add max-width with ellipsis truncation on tag labels, with tooltips only appearing when content exceeds ~50 characters. Also need to set a max-width on tooltips themselves to prevent full-screen stretching.</li> </ul> <h3 id="ccc-naming-context-types">CCC Naming: Context Types</h3> <ul> <li>The team agreed on naming for the two categories of context: <strong>"Local context document"</strong> for static/internal content stored in Drupal, and <strong>"External context"</strong> for dynamic/third-party content.</li> <li>"Source" is reserved as a property of the context item (e.g., PDF, Google Analytics), not a type label. This avoids confusion when the source is described separately from the type.</li> </ul> <h3 id="ccc-context-list-boundaries-display">CCC Context List: Boundaries Display</h3> <ul> <li>Boundaries have been redesigned as include/exclude toggles within each scope category (rather than separate sections). In the list view, items with no exclusions should render nothing &mdash; not the word "None."</li> </ul> <h3 id="ccc-context-list-pill-colors">CCC Context List: Pill Colors</h3> <ul> <li>Decided to keep pills <strong>gray</strong> (dark variant preferred for contrast) in v1. Green/red are reserved for future semantic meaning (success/error states). Blue is not currently available in the pill library.</li> </ul> <h3 id="ccc-subcontext-tooltip-labels">CCC Subcontext Tooltip Labels</h3> <ul> <li>Agreed on: <strong>"Included in [parent name]"</strong> for required items and <strong>"Conditionally included in [parent name]"</strong> for conditional items. Parent name should be wrapped in italics within the tooltip for readability.</li> </ul> <h3 id="ai-agents-collection-claude-code-integration-demo-jamie-">AI Agents Collection &amp; Claude Code Integration (Demo &mdash; Jamie)</h3> <ul> <li>Jamie demonstrated two experimental projects from Marcus: (1) the <strong>AI Agents Collection</strong> module (GitHub) &mdash; dozens of pre-built agents covering content types, views, fields, menus, SDCs, search API, and more, with an orchestrator chatbot that can plan and execute multi-agent workflows; and (2) a <strong>Claude Code integration</strong> into Drupal via a PHP SDK (AI Claude Agent module) that connects Drupal to Claude Code CLI for agent orchestration, skills, memory, and compaction.</li> <li>Both are highly experimental and not intended for production. The team agreed this is best explored at or after DrupalCon Chicago &mdash; pre-Chicago sprint capacity is fully committed. The Agents Collection (not the Claude Code integration) may be evaluated sooner for bringing features into Drupal CMS.</li> </ul> <p><strong>Next Steps:</strong> Explore AI Agents Collection as time permits; defer serious evaluation to DrupalCon Chicago.</p> > Related issue: [Issue #3565725](https://www.drupal.org/node/3565725)