Daily Digest
Daily Digest – 10 May 2026
Shipped
- Context Control Center navigation icon restored — Two merged fixes resolved a broken CSS path that caused the CCC navigation icon to disappear after a DX cleanup pass.
- Context Control Center fatal uninstall error fixed — A missing
ai_context_usagetable was causing SQL crashes inAiContextUninstallValidatoron clean Drupal CMS 2.1 installs; the fix was merged to the1.xbranch. - Context Control Center language scope form tests added — New tests covering scope form rendering and persistence were merged, closing out a Sprint 9 todo item.
Ongoing
- AI module TypeError on base field automation — A fatal
TypeErrorinAutomatorBaseAction::getAutomatorsOptions()when processing base fields has a fix MR with a new kernel test awaiting review. - AI Automators migration to structured output — An open 1,819-line MR replaces pseudo-JSON output in
ai_automatorswith structured output, and two competing MRs also remain open to migrate away fromAiProviderFormHelper. - Context Control Center site architecture context source — Two competing MRs totaling over 19,000 diff lines propose different approaches to adding an
ai_context_site_architecturesubmodule and need reconciliation before either can merge. - Drupal Canvas multi-value field re-add regression — Three separate MRs are open exploring different fix strategies for a regression that prevents re-adding multi-value fields, with no approach yet selected.
- Unstructured document loader — A 1,989-line MR introducing a new document loader component to the Unstructured module is open and awaiting architectural review.
AI (Artificial Intelligence)
Bug Fixes and New Issues
Pieter Frenssen (pfrenssen) filed and submitted a fix for a newly reported crash: TypeError in AutomatorBaseAction::getAutomatorsOptions() when automating base fields. The root cause is that getAutomatorsOptions() requires a $bundle argument, which is not available for base fields since they apply to all bundles, causing a fatal TypeError when isAvailable() is called. The accompanying fix MR includes a new kernel test, AiAutomatorsBaseFieldTest, and is awaiting review.
In-Progress Sprint Work
Several AI Initiative Sprint items saw activity. The Move Automators to Structured Output MR from Ann Mary Sruthy (annmarysruthy) remains open at 1,819 diff lines, replacing pseudo-JSON output in ai_automators with a structured output approach. Two parallel MRs -- from Anjali Prasannan (AnjaliPrasannan) and a rebase variant from Marcus Johansson (Marcus_Johansson) -- address Use the provider configuration element for Automators, migrating away from AiProviderFormHelper. Bruno Bruno (bbruno) posted a large MR (6,722 diff lines) adding a React-based default tools editor for agents, with YAML/interactive tab switching and tool autocomplete. The update hook naming convention documentation MR from Avinash jha (avinash.jha) is a small 24-line change awaiting merge. No commits landed in the reporting period.
How can I help on this project?
- Review the base field TypeError fix MR -- it has tests and manual instructions ready, and just needs a code review to merge.
- The Move Automators to Structured Output issue is unassigned; review the open MR or help reconcile the two competing provider configuration element MRs.
- Pick up the unassigned update hook naming documentation review -- it is a trivial merge candidate.
Drupal AI Initiative
Activity in the last 24 hours was light, with no merged MRs or commits landing during the reporting period. Two new issues were filed by Kristen Pol (kepol) around the Chicago Driesnote demonstration repository at https://github.com/fosterinteractive/c2026/, which is used for live AI CMS comparison demos.
Chicago Driesnote Demo Work
The Update Chicago Driesnote repo to include demo prompts issue is open and unassigned, requesting that prompt content be extracted from an internal Google doc and committed to the repo as a Markdown file. Separately, Fix RAG search on Chicago Driesnote repo install is assigned to Kristen Pol (kepol) and tracks a broken RAG search experience on fresh installs -- the fix may land as either a config change or updated README instructions. Neither issue has a corresponding MR yet, and no root cause for the RAG failure has been identified publicly.
How can I help on this project?
A developer could make an immediate contribution in one of these ways:
- Clone the
fosterinteractive/c2026repo, attempt a fresh install, and diagnose the RAG search failure described in Fix RAG search on Chicago Driesnote repo install. - Pick up the unassigned Update Chicago Driesnote repo to include demo prompts task and open an MR adding a
PROMPTS.mdfile.
Unstructured
Activity on the Unstructured module over the last 24 hours was limited to a single open merge request. Ahmad Khader (Ahmad-Khader) opened Resolve #3582438 "Create document loader", a substantial contribution spanning 1,989 diff lines aimed at introducing a document loader component to the module. The MR remains open and unmerged, with no associated commits landing in the reporting period and no issue comments recorded.
No bugs were fixed, no APIs were merged, and no blockers were explicitly documented during this window. The size of the MR suggests it likely introduces significant new functionality, and it will need thorough review before it can land.
How can I help on this project?
Drupal Canvas
Active Development
No commits landed in the reporting period, but significant MR activity is underway around two related problem areas: multi-value field handling and symmetric content inputs for translation.
Two MRs from Shubham Prakash (shubham.prakash) were closed: one targeting a FormattedText component rendering issue (Issue #3588450) and one addressing re-adding a multi-value field (Issue #3587472). The latter was flagged as AI-assisted and appears to have been superseded by work from Ben Mullins (bnjmnm), who has opened three separate MRs against the same issue: a test-plus-original-fix variant, a backend widget solution, and a test-only MR. This split suggests active investigation into the right fix strategy for the multi-value re-add regression. A large post-multivalue reroll draft (8,546 diff lines) from bnjmnm also remains open.
Separately, Ted Bowman (tedbow) has a draft open for symmetric content inputs, bringing translation parity between content and config entity component trees via tmgmt_content integration. A known issue with relative internal links (internal:/about) is noted in the description.
How can I help on this project?
Review the three competing MRs for Resolve #3587472 "Backend Widget solution" and provide feedback on which approach is preferable. You could also run the test suite against the test-plus-fix MR, or investigate the relative internal link rendering bug noted in the symmetric content inputs draft.
Context Control Center (CCC)
Sprint 9 wrapped up with a flurry of merges during the reporting period as the project transitions into Sprint 10 with RC1 targeting June 2026. Kristen Pol (kepol) landed four commits to the 1.x branch.
Merged and Shipped
Two back-to-back fixes addressed CCC navigation icon missing due to menu changes, caused by CSS path breakage introduced in the DX cleanup pass; both MR 149 and the earlier MR 148 were merged. Fatal uninstall errors on a clean Drupal CMS 2.1 instance -- a missing ai_context_usage table causing SQL crashes in AiContextUninstallValidator -- were resolved via MR 147, closing Fatal errors when uninstalling CCC. Language scope form tests were also added in MR 137, closing out Address todos in scope form rendering and persistence tests.
Open MRs Awaiting Review
Several substantial MRs are queued. Two competing approaches to Add Site Architecture context source for Drupal site behavior contracts are open simultaneously: MR 146 from George Kastanis (zorz) adds an ai_context_site_architecture submodule with an optional ai_context_site_architecture_mcp layer (6,499 diff lines), while MR 126 from scott falconer (scottfalconer) takes a collector/post-processor service approach (13,094 diff lines). These need reconciliation before either can merge. Other open MRs cover selection performance improvements, per-agent and entity schema fields, post_select and post_render events, CKEditor context injection from Jesse Hofmann-Smith (jessehs), config validation using #config_target from Sven Decabooter (svendecabooter), scheduler submodule extraction assigned to Matt Glaman (mglaman), and permissions review from Ann Mary Sruthy (annmarysruthy).
Blockers
Remove AiContextItemType and Fix eslint errors in GitLab UI even when pipeline is green remain labeled blocked. The AiContextItemType removal is explicitly gated on the scheduler submodule work in MR 92. QA scripts for pre-1.0 testing (CCC QA scripts for 1.0 testing) are also unassigned and flagged as a stable blocker.
How can I help on this project?
- Review the two competing site architecture submodule MRs (MR 146 and MR 126) and comment on which approach better fits the plugin architecture.
- Pick up the unassigned CCC QA scripts for 1.0 testing issue to unblock the QA team.
- Review MR 107 replacing manual config gets with
#config_targetinAiContextSettingsForm.
Shipped
- Context Control Center Beta 2 Released — The second beta of the AI Context Control Center was officially released and immediately stabilised, with critical post-release bugs including a fatal uninstall error and a missing navigation icon fixed and merged within hours.
- AI Automators Crash Fix Submitted — A fix was submitted for a crash affecting editors who use AI to automatically populate certain core content fields, addressing a real-world reliability issue for teams using this feature today.
- Drupal Canvas Editor-Facing Rendering Fixes Completed — Two resolved issues around how formatted text and multi-value content fields behave were closed, improving the reliability and consistency of the content editing experience.
Ongoing
- Chicago DrupalCon Demo Preparations at Risk — Work is underway to fix a broken AI-powered search feature and finalise demo scripts ahead of the high-profile Driesnote showcase, but no code has been merged yet and the event deadline is approaching.
- Context Control Center Sprint 10 and Road to 1.0 — The team is working through final gaps before a Release Candidate, including updated interface designs, documentation, a QA testing script, and a setup walkthrough video, with a 1.0 launch targeted for June.
- AI Agent Visual Configuration Editor Under Review — A new point-and-click interface for setting up AI agent tools has been submitted and is awaiting review, replacing a complex manual process that currently limits non-technical users.
- Unstructured Module Document Loader Awaiting Review — A substantial contribution enabling the system to ingest and process content from multiple sources has been submitted but not yet reviewed, creating a bottleneck for a foundational capability.
2026 Capabilities Progress
- Page generation — Drupal Canvas is resolving rendering and multi-value field issues that affect how AI-assembled pages display content reliably. However, competing proposals on multi-value field handling remain unresolved, which is a risk to delivery timelines for this capability.
- Context management — Strong progress today. The Context Control Center shipped its Beta 2 release and is on track for a 1.0 launch in June. New proposals to add site architecture mapping and document ingestion as context sources would meaningfully extend what AI can understand about a site. The next milestone is completing Sprint 10 and entering Release Candidate testing.
- Background agents — The AI Automators component, which triggers AI-driven content field population automatically, received reliability fixes and standardisation work today. A crash affecting certain core content fields was identified and a fix submitted. Progress is real but several related proposals risk stalling without coordinated effort.
- Design system integration — No direct progress today.
- Content creation and discovery — Two advances today: work to make the AI text editor aware of its surrounding content context is progressing, and a fix for broken AI-powered search in the initiative's flagship demo is underway. The demo search failure is a near-term risk to public perception if not resolved before DrupalCon Chicago.
- Advanced governance — No direct progress today.
- Intelligent website improvements — The new visual editor for configuring AI agent tools, submitted today, reduces the technical barrier to setting up agents that can act on site data. This is an early but meaningful step; the capability is still in foundational stages.
- Multi-channel campaigns — No direct progress today.
AI (Artificial Intelligence)
Sprint in Progress: Reliability, Usability, and Quality
The past 24 hours have seen sustained momentum across the AI module, with multiple workstreams advancing in parallel. The focus is on making AI-powered content features more reliable, consistent, and easier to configure for site builders and editors.
A significant area of activity is the Automators component, which automates AI-driven field population on content. Several efforts are converging here: work to improve how AI providers are selected and configured is progressing through two open proposals, and a separate effort aims to standardise how the Automators component processes and returns AI output -- making it more predictable and less error-prone. Alongside this, Pieter Frenssen (pfrenssen) identified and submitted a fix for a crash that occurs when automating certain core content fields, a real-world reliability issue that could affect editors using this feature today.
On the AI Agent front, Bruno Bruno (bbruno) has submitted work on a new visual editor for configuring agent tools, replacing a complex manual process with an interactive interface. This directly reduces the barrier to setting up AI agents for non-technical users.
Smaller but important progress includes a documentation improvement for developer conventions, which supports long-term project maintainability, and ongoing work to enable the AI-powered text editor to be aware of the content context it is operating within.
How can I help on this project?
Leaders can support progress by ensuring contributors working on Automators improvements have dedicated time to reach completion, as several related proposals risk stalling without coordination. Advocating for UX review resources would help unblock the agent tools editor. Encouraging organisational testing of the Automators crash fix would validate it for faster merge.
Drupal AI Initiative
Chicago DrupalCon Demo Preparations Underway
Activity over the past 24 hours has been focused on polishing the AI demonstration materials ahead of the Chicago DrupalCon Driesnote, a high-profile public showcase of Drupal's AI capabilities. Two issues are being addressed to ensure the demo is ready and reproducible.
First, work is underway on Update Chicago Driesnote repo to include demo prompts, which involves capturing the key AI interaction scripts in a shareable format so that anyone setting up the demo environment has clear, consistent prompts to work from. This reduces the risk of an inconsistent or underwhelming live demonstration.
Second, Kristen Pol (kepol) has picked up Fix RAG search on Chicago Driesnote repo install, addressing a known failure in the AI-powered search feature that is central to the demo. Without this fix, a core part of the showcase would not function as intended in front of a large audience.
No code was merged or committed in this period, so the immediate priority is resolving these issues before the event deadline.
How can I help on this project?
Leaders can support progress by confirming the timeline and any hard deadlines for the Chicago demo, ensuring the team has adequate capacity to resolve these issues in time. If external contributors or vendor support are needed to accelerate testing, approving that resourcing quickly would reduce risk to the public showcase.
Unstructured
Summary
Activity on the Unstructured module over the past 24 hours was focused on a single area of development. Ahmad Khader (Ahmad-Khader) opened a new merge request, Resolve #3582438 "Create document loader", which represents meaningful forward progress on the module's core capability. A document loader is the mechanism that allows the system to ingest and process content from various sources, a foundational requirement for any project that aims to handle unstructured data at scale. This is a substantial contribution, reflecting a significant amount of new work. However, the merge request is still open and awaiting review, meaning the work has not yet been formally accepted into the project.
No issues were updated and no commits were merged during this period, so the project's overall pace remains measured. Getting this contribution reviewed and approved in a timely manner would help maintain momentum.
How can I help on this project?
Consider whether additional reviewers or dedicated review time can be resourced to avoid contributions stalling in queue. If this module supports a broader organisational initiative, reinforcing its strategic priority to relevant teams can help accelerate decisions. Funding for a dedicated maintainer could also reduce bottlenecks significantly.
Drupal Canvas
Activity Summary
The past 24 hours saw meaningful development momentum on Drupal Canvas, with several merge requests either completed or actively progressing across two important capability areas.
Two merge requests were closed, indicating resolved work around how formatted text components render and how multi-value content fields behave. These fixes, contributed by Shubham Prakash (shubham.prakash), address editor-facing issues that could affect the reliability and consistency of content entry experiences.
On the translation front, Ted Bowman (tedbow) is progressing a significant piece of work via the Draft: Resolve #3583684 "Symmetric content inputs" merge request. This brings translation support for content managed through Canvas into parity with configuration-based content, an important step for teams managing multilingual sites.
Ben Mullins (bnjmnm) is driving multiple parallel proposals around the handling of multi-value fields, including Resolve #3587472 "Backend Widget solution" and a substantial wider effort tracked in Draft: Post multivalue reroll. The volume of open proposals on this topic suggests the team is working to converge on the right long-term approach, which warrants attention to avoid prolonged indecision.
How can I help on this project?
Consider encouraging decision-makers to review the competing multi-value field proposals and align on a preferred direction, as unresolved options can slow delivery. Ensuring dedicated reviewer capacity is available will help close out open drafts faster. Sponsoring or prioritising the translation work could also unlock significant value for multilingual rollouts.
Context Control Center (CCC)
The past 24 hours saw the Beta 2 release land and a strong wave of quality and stability work close out Sprint 9, while Sprint 10 planning and new feature development got underway in parallel.
Beta 2 Delivered and Stabilised
The Create CCC beta2 release milestone was reached and closed during this period. Immediately after the release, the team addressed several issues that surfaced, including fatal errors when uninstalling CCC and a missing navigation icon caused by a menu change -- both fixed and merged within hours by Kristen Pol (kepol). A round of beta2 QA was also completed and closed.
Significant Feature and Integration Work in Progress
Two separate contributors -- scott falconer (scottfalconer) and George Kastanis (zorz) -- have submitted proposals to add a new Site Architecture context source. This capability would automatically map how a Drupal site is structured and make that understanding available to AI agents, reducing the risk of agents taking incorrect or redundant actions. A proposal to integrate CCC with the Document Loader module is also open, which would allow users to feed PDFs, markdown files, and URLs directly as AI context sources. Jesse Hofmann-Smith (jessehs) has an open contribution to inject context into the rich text editor's AI tools, extending CCC's reach into everyday content editing.
Sprint 10 Planning and the Road to 1.0
Kristen Pol (kepol) formally opened Sprint 10 planning, which runs through 29 May. The focus is on closing remaining gaps before a Release Candidate, including updated user interface designs now being implemented by Aidan Foster (aidanfoster) and Eric Homanchuk (erichomanchuk), documentation improvements, and a QA testing script needed before the Zoocha team can carry out pre-1.0 testing. A configuration walkthrough video is also planned to address reported difficulties with the initial setup experience. Upcoming public appearances -- including presentations at the NYC Drupal AI Summit and DrupalSouth Wellington -- will help grow awareness ahead of the 1.0 release targeted for June.
How can I help on this project?
- Prioritise QA resourcing: The team needs a dedicated QA effort before the Release Candidate. Confirming availability of the Zoocha testing team or equivalent resource now would prevent a bottleneck in June.
- Support community visibility: Endorsing or amplifying the upcoming conference presentations would strengthen adoption ahead of the 1.0 launch.
- Unblock contributor access: Ensuring regular contributors have the platform access they need to collaborate fully remains an open action that leadership can expedite.