Daily Digest
Daily Digest – 17 June 2026
2026 Capabilities Progress
- Page generation — Significant progress on the underlying Canvas AI infrastructure, with work advancing on exposing block props to the agent [55], improving component context handling [54][57], validating AI-generated component data [61], and fixing issues where the AI uses unsupported React libraries [97]. The team also resolved how AI panel state is preserved during refresh [59], which improves the iterative page-building experience.
- Context management — The Context Control Center saw progress on visual improvements for context item display [138][143] and is preparing document loading capabilities for PDFs and web URLs [137]. Work is also underway to document the relationship between AI Best Practices guidance and initiative-specific context [22], establishing a clearer governance hierarchy.
- Background agents — Core automation infrastructure improved with a fix to process multiple queue items per cron run instead of just one [5][17], and work on making automators configurable through subforms [12]. Additionally, progress on enforcing execution principals [8][18] strengthens governance controls for background operations.
- Design system integration — Canvas made substantial progress with merged support for code components that reference entity data [86][89][108][126][127][128][129], enabling AI to work with real content from the site. Infrastructure work also advanced on prop shape validation [82][84][85][125] and JSON Schema consistency [83][123][124], which are foundational for reliable component generation.
- Content creation and discovery — Progress on interactive refinement for field widget automation [14], allowing iterative improvement of AI-generated content. CKEditor integration saw bug fixes for the AI assistant [2][16] and better error handling when provider modules are missing [1]. The AI translate module added error messaging for failed translations [145].
- Advanced governance — Canvas delivered critical translation infrastructure with TMGMT integration for content entities [98][136] and validation constraints preventing data inconsistencies in symmetrical translations [47][109]. Work continues on conflict detection during publishing [105] and auto-save polling [116], with text-based page representations [111] and conflict resolution APIs [117] in draft state.
- Intelligent website improvements — No direct progress today, though foundational work on API testing [9] and the Symfony AI platform provider adoption [19][20] will support future learning and optimization capabilities.
- Multi-channel campaigns — No direct progress today on campaign orchestration or multi-channel content distribution capabilities.
Shipped
- AI module CKEditor bug fixes merged — Fixed a critical error that prevented content editors from using the AI assistant in the text editor [2][16].
- AI module documentation improvements delivered — Added last-modified dates to all documentation pages so users can assess whether guidance is current [3][15].
- AI module queue processing enhancement shipped — Made the number of automation tasks processed during each scheduled run configurable, improving system throughput [5][17].
- Canvas translation infrastructure completed — Enabled professional translation workflows for Canvas pages through TMGMT integration, allowing editors to send component content to translation services [98][136].
- Canvas language-aware rendering fixed — Resolved a bug where embedded media and taxonomy terms displayed in the wrong language instead of matching the current page language [39][102].
Ongoing
- AI module provider platform modernization in progress — Work continues on adopting the Symfony AI component to modernize how the module connects to AI services [19].
- Canvas component version propagation under review — Work is underway to ensure updates to component versions automatically sync across all language variants of a page [36][101].
- Canvas entity reference data structure awaiting product approval — Technical work has been completed but requires stakeholder sign-off on how field properties merge with referenced entity data [71].
- Context Control Center document loader capability in development — New functionality to support PDFs, text files, and web URLs is being built [137].
- AI Agents prompt adherence issue under investigation — An open issue reports that the AI agent does not consistently follow user instructions, requiring investigation to improve reliability [31].
AI (Artificial Intelligence)
The AI module saw heightened community activity over the past 24 hours, with contributors opening 13 issues and submitting 6 merge requests. The work spans quality improvements, user experience fixes, and architectural updates to prepare the module for future releases.
A critical bug was identified and patches were submitted where the CKEditor AI assistant fails when creating content, displaying an error instead of functioning properly. A related usability issue was also addressed: when site builders install the CKEditor AI feature without any provider modules (such as OpenAI), the buttons appear but fail silently—confusing for administrators who expect the feature to work. Contributors submitted fixes for both problems.
Several merge requests advance the module's strategic direction. Work continued on adopting the Symfony AI component as a platform provider, which will modernize how the module connects to AI services. Separately, a contributor proposed adding interactive refinement to field widget automation, allowing editors to iteratively improve AI-generated content—a significant workflow enhancement.
Documentation improvements were also submitted, including a proposal to display last-modified dates on all documentation pages so readers can judge whether guidance is current. Meanwhile, contributors flagged concerns about missing commits between version branches, prompting a review to ensure recent fixes are available in all supported releases.
How can I help on this project?
- Prioritize review and testing of the CKEditor bug fixes to unblock content editors experiencing errors.
- Allocate technical leadership time to validate the version-branch regression analysis and coordinate any necessary backports.
Drupal AI Initiative
Over the past 24 hours, the Drupal AI Initiative completed organizational work to improve how the project manages its marketing activities and documents guidance for AI-assisted development.
Jeremy Chinquist (jjchinquist) merged two changes to streamline project structure. The first removed marketing-related issue templates from the main AI Initiative repository now that they have been migrated to a dedicated marketing initiative repository. This separation clarifies responsibility and reduces duplication. The second update documented the relationship between this project and the AI Best Practices guidance, establishing a clear hierarchy where the best practices repository serves as the foundational authority for development standards, with initiative-specific guidance layered on top.
Additionally, a legacy meta-issue tracking an older marketing sprint was closed, as that work has been migrated to the new marketing repository.
These changes represent progress in maturing the initiative's operational structure, making it clearer where different types of work should be managed and how development guidance is organized across related projects.
How can I help on this project?
- Ensure the marketing initiative has dedicated resources now that it operates in a separate repository with distinct workflows.
- Review and endorse the AI Best Practices guidance framework so teams understand its authority across Drupal AI projects.
OpenAI Provider
The OpenAI Provider module saw progress this period on expanding its capabilities for image manipulation. A merge request was opened by Marcus Johansson (Marcus_Johansson) to add image-to-image possibilities, which will enable users to transform existing images rather than only generating new ones from text. This represents an enhancement to the module's feature set, allowing for more sophisticated image editing workflows within Drupal.
The work is currently under review and has not yet been integrated into the codebase. Once merged, this capability will broaden the types of content creation and editing tasks that can be performed through the platform.
How can I help on this project?
- Ensure the merge request receives timely technical review to keep momentum on the image-to-image feature delivery.
- Consider whether additional use cases or documentation resources are needed to help teams adopt the new image manipulation capabilities once available.
Huggingface Provider
The Huggingface Provider module saw new development activity during the reporting period. A merge request to add extractive question capabilities was opened by Ahmad Khader (Ahmad-Khader). This work aims to expand the module's functionality to support question-answering features, which would allow users to extract specific answers from provided text or documents. The merge request represents active progress toward broadening the types of AI-powered tasks the module can handle, potentially making it more valuable for content-heavy sites and knowledge management use cases.
No commits were merged during this period, and the module appears to be in active development with features being built out incrementally.
How can I help on this project?
- Ensure the team has dedicated review capacity to evaluate and merge the pending question-answering feature work in a timely manner.
- Clarify prioritization for additional AI capabilities to help the team sequence upcoming development work effectively.
Microsoft Azure AI
The Microsoft Azure AI module saw development activity focused on improving user guidance during configuration. Peter Törnstrand (peter_tornstrand) opened a merge request to clarify the model ID field description in the provider setup form. This change will help administrators understand that the value they enter will be directly used when communicating with Azure services, reducing potential configuration errors and support requests.
This work represents incremental progress on making the module more intuitive for site builders who need to integrate Azure AI capabilities into their Drupal applications. Clearer setup instructions reduce the risk of misconfiguration and improve the onboarding experience for new users of the module.
How can I help on this project?
- Allocate code review resources to evaluate and merge the pending configuration improvement work, enabling faster delivery of user-facing enhancements.
- Consider whether dedicated documentation resources are needed to support broader Azure AI adoption across your organization's Drupal properties.
Model Context Protocol
The Model Context Protocol module saw progress on expanding its capabilities during the reporting period. A new merge request was opened to add Write (Create/Update) Operations Support, submitted by Shubham Goel (shubhamgoel). This work will enable the module to not only read data but also create and modify content, representing a significant step forward in functionality. The change involves over 1,200 lines of code and is currently under review.
This enhancement is important for the module's strategic direction as it moves beyond read-only capabilities toward full data management support. Once merged and tested, users will be able to perform a wider range of operations through the protocol.
How can I help on this project?
- Arrange for technical review resources to evaluate the pending merge request, ensuring quality feedback is provided promptly to maintain development momentum.
- Clarify the project's roadmap priorities and release timeline to help contributors understand which features should be prioritized next.
AI Agents
The AI Agents project saw progress on two quality improvements during the reporting period.
A schema error affecting the CKEditor plugin integration has been addressed. This plugin allows AI Agents to work within the text editor, but was generating configuration errors in Drupal. Sven Decabooter (svendecabooter) submitted a merge request to add the missing schema, which will eliminate these validation errors once reviewed and merged. This resolves Schema error for AI Agents CKEditor plugin.
Separately, an issue was opened regarding The agent doesn't do what I say, where the AI agent did not follow specific instructions provided by the user. This relates to how the system interprets and executes prompts, particularly in the automated field-filling feature. The issue is marked as accepted and awaiting investigation. Understanding and fixing prompt adherence is important for user trust and the practical utility of AI-generated content.
How can I help on this project?
- Ensure code review capacity is available to merge the pending CKEditor schema fix, preventing delays in quality improvements.
- Prioritize investigation resources for the prompt adherence issue, as reliability directly impacts user confidence in AI features.
Tool API
The Tool API module saw automated compatibility work initiated this period. A process has begun to ensure the module works with the upcoming Drupal 12 release by identifying and removing uses of deprecated code patterns. This work is being handled by an automated system that periodically scans the codebase and proposes updates.
A merge request with compatibility fixes was opened related to Automated Drupal 12 compatibility fixes for tool 1.0.x-dev. This represents the first step in preparing the module for the next major version of Drupal. No commits were finalized during this period, indicating the changes are still under review.
This compatibility work is standard preparation for platform upgrades and ensures the module will continue functioning when organizations migrate to Drupal 12. The automated nature of the initial detection helps identify issues efficiently, though human review will be needed to validate and merge the proposed changes.
How can I help on this project?
- Assign a developer to review and merge the pending compatibility updates to keep the module ready for Drupal 12 adoption.
- Consider allocating resources for broader testing of the module against Drupal 12 to identify any issues beyond automated detection.
Drupal Canvas
Development activity over the past 24 hours centered on translation infrastructure and data integrity for multilingual sites. The team merged critical work enabling professional translation workflows through TMGMT integration for content entities. This allows editors to send Canvas-powered pages to translation services, with each component's translatable content appearing as a separate string for translators to review—a key requirement for enterprise multilingual publishing. A complementary validation constraint was also merged to prevent data inconsistencies when using symmetrical translation mode, ensuring non-translatable content stays synchronized across language versions.
The team closed a significant bug affecting language-aware rendering of referenced entities (such as media items or taxonomy terms embedded in Canvas pages). Previously, these references displayed in the site's default language rather than matching the current page language. This has now been resolved. Additional work merged includes a browser-based interface for selecting entity field data when configuring code components, and a package version bump preparing the next Canvas UI release.
Work in progress includes further translation capabilities (propagating component version updates across all language variants), improvements to the language selector for content templates, and ongoing enhancements to conflict detection when multiple editors work simultaneously.
How can I help on this project?
- Allocate product management time to review and approve the merged entity reference data structure (Christian López Espínola has flagged Product verification: merging reference field-level field properties with the referenced entity's own data for stakeholder sign-off).
- Prioritize testing resources for the TMGMT translation workflow, particularly around the expected editor experience when translating Canvas pages through external translation services.
Context Control Center (CCC)
The Context Control Center project saw activity across seven issues over the past 24 hours, focused on improving user experience, extending capabilities, and preparing for broader adoption.
The team is working to enhance how context items are displayed and managed. A new full-page layout is being developed through Add full view layout for context item canonical and revision pages based on new design, with an open merge request under review. Separately, the team identified opportunities to streamline the context listing interface through Possible UX improvements on new context listing page, proposing to consolidate columns and reduce clutter. A minor visual alignment issue was also flagged for Show this overview page checkbox is misaligned on vanilla Drupal 11.
Work continued on expanding the system's document handling capabilities through Create Document Loader submodule for CCC, which will support PDFs, text files, and web URLs. An integration gap was identified in hook_ai_context_scope_values_alter() is not honored in scope value forms, where downstream modules cannot properly extend scope values.
The team also began preparing security documentation through Create SECURITY.md file for AI Context (CCC) to establish clear vulnerability reporting procedures.
How can I help on this project?
- Ensure design and UX review resources are available to finalize the visual improvements identified in the listing and display pages.
- Clarify extensibility requirements with stakeholders to guide resolution of the scope customization gap for downstream adopters.
Field Widget Actions
No development activity occurred during this period. The project tracks one open bug report related to user interface clarity: the system currently displays action options to users even when those actions cannot actually be used in their current context. This creates confusion when users attempt to add functionality that appears available but cannot be activated. The issue was previously identified and remains unassigned, with no new progress in the last 24 hours.
This type of usability issue is typical for modules in active development and does not block core functionality. However, it does affect the user experience by requiring users to troubleshoot why certain displayed options don't work as expected.
How can I help on this project?
- Allocate developer resources to address the user interface bug, which would improve usability and reduce user confusion.
- Consider whether this module aligns with strategic priorities and should receive dedicated maintenance support.
AI translate
The AI translate module saw one new development in the past 24 hours. A merge request was opened to improve how the system handles translation failures. Currently, when automated translations fail, users may not receive clear feedback about what went wrong. Miriam Nugent (Peacog) has proposed a solution that will display appropriate error messages when translation attempts are unsuccessful.
This work addresses a user experience gap that could leave content editors uncertain about whether their translation requests completed successfully. Clear error messaging will help users understand when manual intervention is needed and reduce confusion during content workflows.
The merge request is now awaiting review before it can be integrated into the module.
How can I help on this project?
- Ensure code review capacity is available to evaluate and merge the pending error handling improvement in a timely manner.
- Consider whether user-facing error messages need stakeholder or documentation review before release.
LiteLLM AI Provider
The LiteLLM AI Provider module saw minimal activity over the past 24 hours. A routine automated maintenance update was merged by the Project Update Bot on June 17th. This type of automated housekeeping helps ensure the module stays aligned with Drupal project standards and tooling requirements.
No new features, bug fixes, or user-facing changes were delivered during this period. The module continues in steady state with no active development or issue resolution visible in the reporting window.
How can I help on this project?
- Evaluate whether this module aligns with current organizational priorities for AI integration, and communicate strategic direction to potential contributors.
- Consider allocating development resources if expanded AI provider capabilities are needed for upcoming business initiatives.
AI powered Search Block
A configuration issue affecting how long user search logs are retained has been identified and fixed. The module was silently deleting logs after 7 days, even though the administration interface indicated they would be kept for one year. This discrepancy meant administrators could not rely on search data for quarterly or annual reporting and analysis.
Contributor wouters_f (wouters_frederik) opened a merge request to fix the log expiration setting, which corrects the underlying configuration and ensures the system respects the intended one-year retention period. Once merged, this will align actual behavior with what users see in the settings, restoring confidence in search analytics and historical data availability.
How can I help on this project?
- Prioritize code review and approval of the pending configuration fix to restore proper log retention
- Consider whether the module roadmap requires dedicated maintainer time or community engagement to reach stable release
FlowDrop UI Agents
Development work is underway to address security and operational concerns in the FlowDrop UI Agents module. A new issue was opened to Integrate url whitelisting and add the ability to get agent parameters dynamically, raised by David Galeano (gxleano). The work aims to prevent the system from making unrestricted outbound requests, which could expose the organization to security vulnerabilities and compliance issues. Currently, any changes to agent parameters require code modifications and redeployment, creating operational friction and slowing response times.
The planned improvements will introduce controls over which external services the system can communicate with, reducing exposure to potentially malicious or unauthorized endpoints. Making agent parameters adjustable without code changes will enable faster configuration updates and reduce dependency on engineering resources for routine adjustments.
No code has been merged in the past 24 hours. This issue remains open and unassigned, which is normal for modules in active development.
How can I help on this project?
- Assign engineering resources to prioritize the open security and configuration issue, ensuring timely implementation of URL controls and dynamic parameters.
- Clarify compliance requirements for outbound requests to help shape the whitelisting approach and reduce rework.
Twig to SDC
During this period, the Twig to SDC module saw minimal automated maintenance activity. An automated maintenance process opened a draft merge request containing routine updates generated by the Project Update Bot. This represents standard housekeeping rather than feature development or bug fixes.
No commits were finalized, no user-reported issues were addressed, and no community discussion occurred during the 24-hour window. The module appears to be in a quiet maintenance phase with no active development momentum or user engagement visible in this reporting period.
How can I help on this project?
- Evaluate whether this module aligns with current strategic priorities and consider whether continued investment or sunsetting is appropriate given the low activity level.
- If the module remains strategically important, allocate dedicated development resources to advance it toward a stable release and actively address user needs.
References
[1] Improve ai_ckeditor UX when no provider modules are installed
[2] Issue when creating content and click on AI Assistant on Ckeditor
[3] Show last-modified date on documentation pages (mkdocs-git-revision-date-localized-plugin)
[5] Only one AI Automator worker queue item is processed per cron execution
[9] Do popular provider api test on tagging
[12] Let AiAutomatorFieldProcessInterface (worker types) provide a configuration subform
[14] Issue #3586468: "Add interactive refinement capability to Field Widget Actions Automation"
[15] Issue #3586541 Show last-modified date on documentation pages...
[16] Issue #3586545: Fix null pointer exception in...
[17] Issue #3575190: Add configurable queue items per cron for AI Automators
[18] Resolve #3574723 "Enforce execution principal"
[19] feat: #3586427 Adopt symfony/ai component v0.8 as platform provider
[20] #3586470 "Make API explorer work with Symfony platform and legacy providers"
[22] docs: Document ai_best_practices as the foundational/parent AI-guidance layer
[31] The agent doesn't do what I say
[36] Symmetric translation: component instance version updates must propagate to all translations
[54] Canvas AI: Component context required props missing required flag
[55] Canvas AI: Expose Props of Blocks to the Agent
[57] Canvas AI: Create 'canvas_ai.component_description.settings' config on install
[59] AI panel should preserve its state on refresh
[61] Canvas AI: Drupal\canvas_ai\AiResponseValidator fails to validate non-existent props
[86] Add HostEntityPropSource so content-entity-reference props can resolve to the rendering host entity
[97] AI continues to use unsupported React libraries while creating a component
[98] Add TMGMT translation integration for content entities
[111] Draft: feat(Conflict detection): #3591668 "Text-based Page entity representation via Canvas API"
[116] feat(Conflict detection): #3589076 "Detect conflicts during auto-save polling"
[123] chore: #3587673 Introduce JsonSchemaObjectRef enum
[124] Use draft-07 consistently in backend and frontend.
[125] fix(Shape matching): #3591629 Strip `$id` as well as `id` when normalizing resolved prop schemas
[126] feat: #3587374 Add HostEntityPropSource class and PropSource enum case
[127] chore(Data model): #3585298 Add dataDependencies.entityFields to JavaScriptComponent
[128] feat(Data model): #3591638 Add a computed `src` field property to the image field type
[136] Resolve #3590948 "Add TMGMT translation integration for content entities"
[137] Create Document Loader submodule for CCC
[138] Add full view layout for context item canonical and revision pages based on new design
[143] Issue #3586220: Add single context item display.
[145] fix: #3542014 Display error message when translation fails
Shipped
- TMGMT translation integration for Canvas content entities — Canvas component trees now expose translatable props as separate strings in the TMGMT review UI [98][136].
- Canvas Evaluator respects referencing entity language — The Evaluator now correctly evaluates referenced entities in the referencing entity's language or falls back to negotiated content language [39][102].
- Symmetric translation validation constraint for Canvas — A validation constraint similar to core's ContentTranslationSynchronizedFieldsConstraint ensures non-translatable input keys maintain identical values across symmetrical translations [47][109].
- Typed Data browser UI for content-entity-reference props — Code component developers can now select entity field data dependencies through a modal dialog for single-target-bundle references [44][108].
- LiteLLM automated maintenance fixes — Automated project maintenance changes were merged to keep the module updated [146].
Ongoing
- AI CKEditor null pointer exception fix — A fix for null pointer exception in AiCKEditorPluginBase when using the AI Assistant button is awaiting review [2][16].
- Configurable queue items per cron for AI Automators — Currently only one AI Automator worker queue item processes per cron execution, a fix is under review to make this configurable [5][17].
- Symfony AI component v0.8 adoption — Major work is in progress to adopt the Symfony AI component as a platform provider [19].
- Canvas symmetric translation component version propagation — Component instance version updates need to propagate to all translations, blocked on validation constraints [36][101].
- MCP write operations support — A merge request adding create and update functionality to the Model Context Protocol module is under review [29].
AI (Artificial Intelligence)
The AI module saw active issue reporting and MR development over the past 24 hours, with contributors opening several new merge requests while no commits were merged to the main branch.
Avinash jha (avinash.jha) opened two fixes targeting recently reported bugs: MR !1683 addresses a null pointer exception in AiCKEditorPluginBase->buildCkEditorModalForm() when using the AI Assistant button in CKEditor 5, and MR !1684 adds the mkdocs-git-revision-date-localized-plugin to show last-modified dates on documentation pages.
Several new issues were filed, including validation problems in AiPromptSubForm when multiple ai_prompt elements with different prompt types exist on a form, and a regression where commits present in 1.3.x were missing from the 1.4.x branch.
Active development continues on the Symfony AI component adoption (MR !1619) and interactive refinement for Field Widget Actions (MR !1629), both with substantial diff sizes indicating major feature work in progress.
How can I help on this project?
Review MR !1683 for the CKEditor null pointer fix, which is marked RTBC. Test MR !1684 for documentation timestamps and verify the mkdocs plugin integration. Investigate the AiPromptSubForm validation issue with multiple prompt elements to help identify the root cause.
Drupal AI Initiative
The Drupal AI Initiative shipped documentation and repository cleanup work over the past day. Jeremy Chinquist (jjchinquist) merged two MRs focused on organizational improvements.
The docs: Document ai_best_practices as the foundational/parent AI-guidance layer MR updated README.md to formally establish the ai_best_practices project as the parent authority for AI-assisted development guidance. This mirrors the precedence model already in use in ai_initiative_marketing, where initiative-specific guidance defers to the foundational layer by default.
Repository cleanup continued with chore: Remove Marketing issue templates migrated to ai_initiative_marketing, which removed five Marketing-specific issue templates (Blog Entry, Case Study, Generic, Video, and Webinar) now that the AI Marketing Initiative has its own dedicated repository. These templates were duplicated into ai_initiative_marketing and should live exclusively there.
Additionally, the Marketing Sprint #3: May 11 - 25 [Meta] issue was closed as it has been migrated to the marketing repository.
How can I help on this project?
Review open merge requests to provide feedback on proposed changes. Check the issue queue for unassigned tasks that need attention. Consider contributing documentation improvements to clarify the relationship between ai_initiative and ai_best_practices as the new precedence model is adopted.
OpenAI Provider
Activity in the OpenAI Provider module over the past 24 hours was limited to a new merge request. Marcus Johansson (Marcus_Johansson) opened Resolve #3593019 "Add imagetoimage possibilities", which introduces image-to-image transformation capabilities to the module. The MR contains 258 lines of diff and is currently awaiting review. No commits were pushed or merged during the reporting period.
How can I help on this project?
Developers can contribute by reviewing the open image-to-image possibilities MR to help validate the implementation and accelerate its path to merge. Testing the new functionality against OpenAI's API would be particularly valuable.
Huggingface Provider
Activity this period focused on expanding the module's capabilities with a new merge request from Ahmad Khader (Ahmad-Khader). The Resolve #3584375 "Add extractive question" MR remains open for review, introducing 100 lines of changes on the 3584375-add-extractive-question branch. This work aims to add extractive question answering functionality to the Huggingface provider.
No commits were pushed or merge requests merged during the reporting period, indicating the MR is awaiting review and testing before integration. No blocking issues were reported in the available data.
How can I help on this project?
- Review and test the Add extractive question MR to help move it toward merge, particularly validating the API integration with Huggingface's question answering models.
- Check the module's issue queue for unassigned bugs or feature requests that need attention.
Microsoft Azure AI
The Microsoft Azure AI module saw modest activity in the past 24 hours with one new merge request opened. Peter Törnstrand (peter_tornstrand) submitted Alter description for model ID field in AzureProvider form to make clear the..., which updates the description text for the model ID field in the AzureProvider form to clarify that the entered value will be used directly in Azure API requests. The merge request spans 174 lines of changes and is awaiting review. No commits were merged during this period, indicating that development focus may be shifting toward documentation and user experience improvements in the provider configuration interface.
How can I help on this project?
- Review MR 23 to validate that the updated model ID field description is clear and accurate for Azure integration.
- Test the merge request against various Azure AI deployment scenarios to ensure the description aligns with actual API behavior.
Model Context Protocol
The Model Context Protocol module saw focused development activity with progress on write operation capabilities. Shubham Goel (shubhamgoel) opened a substantial merge request for Write (Create/Update) Operations Support, contributing over 1,200 lines of changes to enable create and update functionality in the module. The MR remains open and awaiting review.
No issues received updates or comments during this period, and no commits were merged to the main branch, suggesting the project is in an active development phase with contributors working on feature branches.
How can I help on this project?
- Review the pending Write (Create/Update) Operations Support merge request to help move write operations functionality toward completion.
- Test the write operations branch against your Drupal installation to identify edge cases or integration issues before merge.
AI Agents
The AI Agents module saw focused activity around configuration schema this period. Sven Decabooter (svendecabooter) opened Add CKEditor schema for ai_agents (!221) to resolve schema errors affecting the AICKEditor plugin integration. The MR addresses Schema error for AI Agents CKEditor plugin, which had been causing Drupal's schema validation to report errors for the AI CKEditor module integration.
Separately, Marcus Johansson (Marcus_Johansson) opened The agent doesn't do what I say, an accepted bug report concerning agent behavior in the AI Automators submodule. The issue appears related to advanced prompt templates that embed tokens for entity fields, though no merge request has been submitted yet.
No commits were merged during this 24-hour period. Progress on the CKEditor schema fix is blocked pending review of !221.
How can I help on this project?
- Review !221 to help merge the CKEditor schema fix.
- Investigate and submit a patch for The agent doesn't do what I say, which is unassigned and needs a solution for prompt template handling.
Tool API
The Tool API module saw automated Drupal 12 compatibility work during this period. The Project Update Bot opened Automated Drupal 12 compatibility fixes for tool 1.0.x-dev along with Automated Project Update Bot fixes (MR !94), which addresses deprecated API usage. The merge request targets the project-update-bot-only branch and contains 47 lines of changes from run 12-848511. No commits were merged during this period, and the automated MR remains open awaiting review from maintainers.
How can I help on this project?
Drupal Canvas
Significant progress on multilingual support this period, with several major features merged. TMGMT translation integration for content entities landed via MR !1232, enabling Canvas component trees to expose translatable props as separate strings in the TMGMT review UI. The Evaluator now respects the referencing entity's language when evaluating referenced entities (Evaluator must respect the referencing entity's language), merged via MR !876 by Shubham Prakash (shubham.prakash), Ignacio Sánchez Holgueras (isholgueras), Lee Rowlands (larowlan), and Wim Leers (wimleers). A validation constraint similar to core's ContentTranslationSynchronizedFieldsConstraint was added (MR !1248) to guarantee symmetrical translations maintain identical values for non-translatable input keys, contributed by Ted Bowman (tedbow) and Wim Leers (wimleers).
The "Typed Data browser" UI for content-entity-reference props shipped via MR !1182, merged June 17, enabling code component developers to select entity field data dependencies through a modal dialog. This work by wotnak and Christian López Espínola (penyaskito) handles single-target-bundle references. The drupal-canvas package was bumped to 0.4.2 by Harumi Jang (hooroomoo).
Several critical issues were closed, including normalizePropSchema() strips id but resolver writes $id, which prevented object $ref props from registering correctly. A fix for Fallback component config schema validation (MR !1246) was merged by Christian López Espínola (penyaskito), preventing rejection of existing inputs when a component's defining module is removed.
Work continues on symmetric translation support, with MR !1163 open to propagate component instance version updates to all translations. Progress is blocked on validation constraints and config entity translation validation, which core does not currently support (Validate translations of Canvas' config entities).
How can I help on this project?
- Review MR !1163 for symmetric translation component version propagation, which needs testing across multiple languages.
- Pick up Canvas AI: canvas_ai_post_update_0003 strips the orchestrator agent UUID, which is unassigned and needs a fix for setData() dropping the uuid key.
- Review MR !1249 addressing the infinite redirect loop when using invalid langcode prefixes.
Context Control Center (CCC)
Activity over the past 24 hours centered on planning and issue refinement rather than code integration. Six issues were updated, covering UI improvements, extensibility, and developer experience.
On the extensibility front, hook_ai_context_scope_values_alter() is not honored in scope value forms was assigned to Ahmad Khalil (ahmad-khalil-imagex). The issue highlights that the hook exists but is only called in AiContextScopeManager::getAllScopeValues(), which is not consumed by the scope subscription UI (AiContextAgentForm) or context item forms, blocking downstream modules from extending scope values.
UX work continues with Add full view layout for context item canonical and revision pages based on new design, assigned to Eric Homanchuk (erichomanchuk), which has MR !151 open with over 5,800 diff lines. Kristen Pol (kepol) opened Possible UX improvements on new context listing page, proposing to combine Use Case and Scope columns and remove the Scope filter.
New issues include Create Document Loader submodule for CCC, which aims to support PDF, text/MD, and URL loading in MDXEditor, and minor fixes like Show this overview page checkbox is misaligned on vanilla Drupal 11. A SECURITY.md file was also requested.
How can I help on this project?
- Review MR !151 for full view layout for context item pages, testing the two-column layout and subcontext navigation.
- Pick up the unassigned SECURITY.md file creation by copying from AI core.
- Fix the checkbox alignment issue on vanilla Drupal 11 without breaking Drupal CMS.
Field Widget Actions
Activity remains quiet for Field Widget Actions over the past 24 hours. An issue titled Field Widget Actions show in the "Add New Action" unavailable tools was updated on 2026-06-17. The bug concerns the isAvailable method in Field Widget Actions plugins: while this method is used to check availability in AI Automators contexts, the dropdown list for adding new actions does not respect these checks. Currently, only base field type and field widget checks are performed, leading to plugins appearing in the "Add New Action" list even when they cannot actually be added due to missing automators for the entity type and field combination. This creates confusion in the user interface when the "Add" button fails to work as expected.
No merge requests were opened or merged, and no commits were pushed during this reporting period. The issue remains unassigned with no related MRs.
How can I help on this project?
- Pick up the Field Widget Actions show in the "Add New Action" unavailable tools bug and develop a patch that filters the dropdown list using the isAvailable method.
- Review the current isAvailable implementation to ensure it provides adequate checks for all relevant contexts beyond AI Automators.
AI translate
A new merge request was opened in the last 24 hours addressing error handling in the translation process. Miriam Nugent (Peacog) submitted fix: #3542014 Display error message when translation fails, which implements proper error messaging when translation operations fail during batch processing. The MR contains 89 lines of changes and is currently awaiting review.
No commits were merged during this reporting period, leaving the open MR as the primary focus for immediate activity.
How can I help on this project?
LiteLLM AI Provider
The LiteLLM AI Provider module saw minimal activity in the past 24 hours. A single automated merge request, Automated Project Update Bot fixes, was merged on 2026-06-17. This MR was created by Project-Update-Bot and contains automated project maintenance changes from run 12-839256, totaling 13 lines of diff. The changes relate to issue #3594751, which appears to be part of ongoing automated project maintenance efforts across Drupal projects.
No manual commits, bug fixes, or API changes were introduced during this reporting period. The module appears to be in a stable maintenance phase with no blocking issues or active development requiring immediate attention.
How can I help on this project?
With no active merge requests or recent development activity, contributors could help by reviewing the module's issue queue for any unaddressed bugs or feature requests that may need triage. Testing the module with the latest Drupal core and AI-related modules would help identify compatibility issues.
AI powered Search Block
A new merge request was opened by wouters_f (wouters_frederik) addressing a configuration mismatch in the logging subsystem. The Fix log expiration setting not being respected MR resolves an issue where the module's install configuration file was missing, causing log retention to default to 7 days in the helper code while the settings form displayed 1 year as the default. This discrepancy meant administrators believed logs were retained for a year when they were actually purged weekly. The fix adds the missing config/install/ai_search_block_log.settings.yml file and updates the helper fallback value to align with the form default of 'year'.
No merge requests were merged and no commits were pushed during this reporting period. The open MR currently blocks proper log retention configuration for new installations.
How can I help on this project?
- Review the open log expiration setting MR to verify the config schema matches the new install file and test the helper fallback behavior.
- Check if related update hooks are needed for existing installations that may have incorrect ai_search_block_log.settings values.
FlowDrop UI Agents
Activity remained quiet over the past 24 hours with no merges or commits. The primary focus is on Integrate url whitelisting and add the ability to get agent parameters dynamically, which aims to address security concerns around unrestricted outbound requests and eliminate the need for redeployments when updating agent parameters. The issue, opened by David Galeano (gxleano), depends on upstream work in the ai_agents module and remains unassigned with no related merge requests yet.
The lack of URL whitelisting currently poses potential security and compliance risks, while static parameter definitions create unnecessary deployment overhead. Progress is blocked pending the integration work from the related ai_agents issue.
How can I help on this project?
- Pick up Integrate url whitelisting and add the ability to get agent parameters dynamically, which is unassigned and awaiting implementation once the ai_agents dependency is resolved.
- Review the upstream ai_agents work to understand the API changes that will need integration.
Twig to SDC
Activity on the Twig to SDC module remained quiet over the past 24 hours, with no merged changes or resolved issues. A draft merge request titled Automated Project Update Bot fixes was opened by Project-Update-Bot (Project-Update-Bot), containing automated project maintenance updates from run 12-848511. The MR remains in draft state with no commits merged to the main branch during this period.
No contributors were active on issue queues or code review during this reporting window, and no blocking issues were identified in the available data.
How can I help on this project?
- Review the Automated Project Update Bot fixes merge request to assess whether the automated changes are appropriate and can be moved out of draft status.
- Check the project's issue queue for unaddressed feature requests or bug reports that could benefit from patches or testing.
References
[2] Issue when creating content and click on AI Assistant on Ckeditor
[5] Only one AI Automator worker queue item is processed per cron execution
[16] Issue #3586545: Fix null pointer exception in...
[17] Issue #3575190: Add configurable queue items per cron for AI Automators
[19] feat: #3586427 Adopt symfony/ai component v0.8 as platform provider
[29] 3551588: Write (Create/Update) Operations Support
[36] Symmetric translation: component instance version updates must propagate to all translations
[98] Add TMGMT translation integration for content entities
[136] Resolve #3590948 "Add TMGMT translation integration for content entities"