Daily Digest
Daily Digest – 5 July 2026
2026 Capabilities Progress
- Page generation — Ongoing work on Canvas workspace autosaves and translation settings [8][9] improves the foundation for page creation workflows, though no direct progress on AI-driven page generation occurred today.
- Context management — Significant progress with accessibility improvements to the Context Control Center interface [14][18], subcontext scope override functionality [15], and preparation for the beta3 release targeting July 6th [10][11][12][13][16][17].
- Background agents — Two new agent skills were proposed to enable self-configuration of guardrails and AI settings [1][2], expanding automated system management capabilities. Additionally, an image classification automation action was proposed for the ECA integration [5], which would enable triggered AI workflows.
- Design system integration — No direct progress today.
- Content creation and discovery — A new AI reranking processor for Search API was proposed [3], which would improve search precision across the platform. The AI Related Content module completed security hardening [20][23][24], strengthening content discovery foundations, while work continues on Drupal 10 compatibility [19][21][22].
- Advanced governance — Work continues on Canvas workspace autosaves [8], which supports draft content versioning. The proposed guardrails agent skill [1] would automate governance configuration, though implementation has not yet begun.
- Intelligent website improvements — No direct progress today.
- Multi-channel campaigns — No direct progress today.
Shipped
- AI Related Content: Drupal 10 compatibility completed — Work is underway to support Drupal 10, which will extend the module's lifecycle and broaden the potential user base as the platform evolves [21][22].
- AI Related Content: Security hardening merged — Access checks were strengthened and clearer configuration guidance was added to help administrators deploy the module more securely [23][24].
- Context Control Center: Database schema reserved for future features — Schema fields needed for upcoming capabilities were reserved ahead of the beta3 release [16].
- Context Control Center: Accessibility improvements in progress — Work is underway to improve screen reader support for filtered lists in forms and tables [18].
- Canvas: Dependency updates applied — Several accessibility and build tool dependencies are being updated to their latest versions to keep the project current and secure [7].
Ongoing
- AI module: Agent-driven configuration capabilities in development — Two new automation features are being designed to allow the system to configure guardrails and general AI settings through conversational commands rather than manual administration [1][2].
- AI module: Search reranking processor proposed — A new feature would improve search precision by re-ordering results using dedicated ranking models, making this capability available across the Drupal search ecosystem [3].
- Context Control Center: Beta3 release in progress — The release is targeted for July 6th, with work underway on contribution statistics, release process standardization, and scope override functionality [10][12][13][15].
- Canvas: Draft content workspace handling under review — A substantial effort to improve how draft content autosaves are managed is in progress [8].
- Canvas: Translation settings experience being refined — Work is underway to clarify how translation and language settings work for users [9].
AI (Artificial Intelligence)
Development activity this period focused on expanding the module's agent-driven automation capabilities and semantic search features. Three new feature proposals were opened, signaling continued investment in making AI functionality easier to configure and more powerful for end users.
Two related automation tasks were defined to allow the system to configure itself through conversational commands rather than manual administration. The first, Add a setup-guardrails agent skill, would enable automated configuration of safety controls and content filters. The second, Add a configure-ai-settings agent skill, would allow general system settings—such as which AI providers and models to use—to be managed through agent commands. Together these would reduce the manual overhead of deploying and maintaining AI-powered features.
A third proposal, Add an AI reranking processor for Search API, aims to improve search precision by re-ordering results using dedicated ranking models, making the feature available to the broader Drupal search ecosystem rather than a single module.
Work also continued on the module's event system, with a merge request in progress to support richer metadata and event hooks during AI operations.
How can I help on this project?
- Confirm strategic priority for agent-driven configuration features relative to other roadmap items, so engineering effort can be sequenced appropriately.
- Identify pilot users or partners who could validate the search reranking feature once development begins.
Contributors: Alphons Jaimon (AJV009)
AI Integration - ECA
This module connects AI capabilities to Drupal's Event-Condition-Action (ECA) automation framework, allowing site workflows to trigger AI operations without custom code.
During this period, work began on extending the module's automation coverage. A new task was opened to add support for image classification workflows. Currently, the module supports automating text-based AI operations such as chat, content moderation, and speech conversion. The new work will allow non-technical site builders to create automated workflows that classify or tag images using AI, for example automatically categorising uploaded photos or detecting content in user-submitted images. This expands the range of business processes that can be automated through the platform's visual workflow builder.
The module is progressing toward its 1.0.0 release. An open task during early development is normal and does not indicate delivery risk.
How can I help on this project?
- Confirm whether image classification automation is a priority for the 1.0.0 roadmap or can be deferred to a later release.
- Identify internal use cases or customer workflows that would benefit from automated image processing to help validate requirements.
Drupal Canvas
Activity over the past 24 hours focused on dependency maintenance and user experience improvements for multilingual capabilities.
A merge request was opened to update several accessibility and build tool dependencies to their latest versions, keeping the project current with external libraries. Separately, work continued on Stage Canvas autosaves in a dedicated Workspace, a substantial effort to improve how draft content is handled. Additionally, a new merge request addresses Fix high level translation settings experience for Canvas, aimed at clarifying how translation and language settings work for users.
The automated dependency tracking system flagged configuration warnings related to rate limits and authentication tokens for external services. These do not impact core functionality but may slow down automated maintenance processes if unresolved.
Overall, progress remains steady with ongoing refinements to content workflows and translation features, alongside routine maintenance to keep dependencies secure and up to date.
How can I help on this project?
- Review and prioritize the pending merge requests on workspace autosaving and translation settings to accelerate user-facing improvements.
- Allocate resources to configure service authentication tokens, which will streamline automated dependency updates and reduce maintenance overhead.
Contributors: **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Gábor Hojtsy (goba), Lauri Timmanee (lauriii)
Context Control Center (CCC)
Progress continued toward the beta3 release, which is planned for completion by July 6th. Work focused on release preparation and improving the user interface for better accessibility.
Several pre-release tasks were completed, including the reservation of database schema fields needed for future features and the gathering of contribution statistics for release notes. The project is now tracking both code and non-code contributions to properly recognize all participants in the release documentation. A formal release process and template is being created to standardize future releases.
Development work is underway on accessibility improvements for forms and tables, including better screen reader support for filtered lists. Separately, work continues on allowing subcontexts to override parent scope settings, giving administrators more granular control over how context hierarchies behave.
The beta3 release itself remains open, awaiting completion of must-have items before final packaging.
How can I help on this project?
- Ensure testing resources are available to validate the beta3 release before the July 6th deadline, particularly for the accessibility improvements already in development.
- Consider whether formal documentation resources are needed to complement the new release process being created.
References
[1] Add a setup-guardrails agent skill to configure guardrails, guardrail sets, and global guardrails
[3] Add an AI reranking processor for Search API (owned by the AI module)
[5] Add ECA execute action for Image Classification
[7] fix(deps): update npm minor and patch
[8] Draft: Stage Canvas autosaves in a dedicated Workspace
[9] Fix high level translation settings experience for Canvas
[10] Gather CCC contribution stats for code and non-code contributions for release notes
[11] Reserve pre-RC1 entity schema fields for CCC
[13] Create a CCC release process and template
[14] Clean up CCC form and table accessibility cleanup
[15] Allow subcontext scope to override parent scope
[16] Issue #3586161: Add entity schema fields.
[17] Issue #3586251: Update subcontext feature help text and docs.
[18] Issue #3586304: Clean up CCC form and table accessibility cleanup
[20] Access checks hardening prior to stable
[21] Resolve "Drupal 10 compatibility" 2x
[22] Resolve "Drupal 10 compatibility" 1x
Shipped
- AI Context entity schema fields in progress — Proposed nullable datetime fields for review_by and auto_expiration, plus status and category fields to AiContextItem entities in preparation for RC1[16].
- AI Related Content access hardening completed — Merged access control improvements and Search API configuration warnings to strengthen security before stable release[23][24].
- AI Related Content Drupal 10 compatibility partially merged — Merged fixes for legacy hook requirements, though additional compatibility work remains in progress[22].
- Canvas npm dependencies update in progress — Proposed update to @axe-core/playwright from 4.11.1 to 4.12.1 and other minor/patch npm package updates[7].
- AI Context accessibility improvements in progress — Proposed Drupal.announce() result counts for JavaScript filters and replacing disabled read-only selects with text in AiContextAgentForm[18].
Ongoing
- AI module InputInterface metadata bag under review — 1335-line merge request adds free-form metadata bag to InputInterface and seeds pre/post/streaming events from ProviderProxy[4].
- Canvas workspace-based autosave in development — Draft merge request with over 4,600 lines implements staging Canvas autosaves in a dedicated Workspace[8].
- AI reranking processor for Search API proposed — New issue to move reranking support into AI module as a Search API processor using the rerank operation type[3].
- AI agent configuration skills in planning — Two new issues propose agent skills for configuring guardrails and general AI settings through the Tool module rather than admin UI[1][2].
- AI Related Content Drupal 10 compatibility incomplete — Additional merge request remains open to complete Drupal 10 compatibility work[21].
AI (Artificial Intelligence)
Development activity over the past 24 hours focused on scoping new agent skills and event infrastructure, though no merges or commits landed during this window.
Three new issues were opened and assigned to expand the module's agent skill library for site configuration. Add a setup-guardrails agent skill to configure guardrails, guardrail sets, and global guardrails and Add a configure-ai-settings agent skill for general AI settings both propose new skills under ai/.agents/skills/ that will drive configuration through the Tool module rather than requiring manual admin UI interaction. Meanwhile, Add an AI reranking processor for Search API proposes moving reranking support into the AI module itself as a Search API processor, leveraging the rerank operation type added in #3488114.
An open merge request on issue #3581952 adds a free-form metadata bag to InputInterface and seeds pre/post/streaming events from input metadata in ProviderProxy, spanning 1335 lines of diff. This work remains under review.
How can I help on this project?
Review the InputInterface metadata bag and event seeding MR to help unblock event hook infrastructure. Pick up the Search API reranking processor feature if you have experience with Search API processor plugins. Test and provide feedback on the proposed agent skill architecture.
Contributors: Alphons Jaimon (AJV009)AI Integration - ECA
Activity remained quiet over the past 24 hours with no merge requests or commits pushed. The module's integration layer between the AI module and ECA (Event-Condition-Action) continues to track coverage gaps for AI operation types.
The outstanding Add ECA execute action for Image Classification issue was updated during the reporting period. This task targets the missing ECA action plugin for the ImageClassification operation type, which would follow the established pattern in existing action plugins (Chat, Embedding, Moderation, Speech to Text, Text to Speech) by extending AiConfigActionBase. The proposed implementation would expose ImageClassification capabilities to ECA flows, allowing site builders to trigger image classification operations through the ECA UI without custom code.
How can I help on this project?
Pick up the unassigned Image Classification action task and implement the Plugin\Action\ImageClassification class following the existing action plugin patterns. Review the existing Chat.php implementation as a reference for extending AiConfigActionBase and building the appropriate Input class.
Drupal Canvas
Activity this period focused on dependency management and ongoing feature development. A merge request to update npm minor and patch dependencies was opened, updating @axe-core/playwright from 4.11.1 to 4.12.1 among other package updates. The Dependency Dashboard continues to surface warnings about rate limits and missing GitHub tokens affecting release notes retrieval.
Two significant feature branches remain in progress. Work continues on staging Canvas autosaves in a dedicated Workspace, a large changeset spanning over 4,600 lines that introduces workspace-based autosave functionality. A new merge request was opened to fix high level translation settings experience for Canvas, addressing explanation of language support limitations across varied use cases with approximately 200 lines of changes.
How can I help on this project?
Review MR 1056 for workspace-based autosave functionality, testing the update hooks and publishing workflow. Review MR 1303 to validate translation settings improvements. Test npm dependency updates for compatibility issues.
Contributors: **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Gábor Hojtsy (goba), Lauri Timmanee (lauriii)
Context Control Center (CCC)
Activity focused on release preparation and accessibility improvements. The Reserve pre-RC1 entity schema fields for CCC issue was closed, completing the addition of nullable datetime fields for review_by and auto_expiration to AiContextItem entities, along with status and category fields. The Gather CCC contribution stats for code and non-code contributions for release notes issue was also closed, addressing the need for comprehensive contributor tracking beyond code commits.
Planning continued for the upcoming beta3 release, with Create CCC beta3 release targeting July 6, 2026 and blocked by must-have issues. A related Create a CCC release process and template issue was opened to formalize the release workflow including contributor attribution.
Work progressed on Clean up CCC form and table accessibility cleanup with an open merge request addressing Drupal.announce() result counts for JavaScript filters and replacing disabled read-only selects with text in AiContextAgentForm.php. The Allow subcontext scope to override parent scope issue remains in manual testing phase.
How can I help on this project?
Review the open accessibility cleanup merge request which includes Drupal.announce() improvements and form modifications. Help with manual testing on the subcontext scope override functionality. Check the beta3 milestone for additional issues needing attention before the July 6 release.
Contributors: Juan Correa (jucs7), Kristen Pol (kepol)References
[1] Add a setup-guardrails agent skill to configure guardrails, guardrail sets, and global guardrails
[3] Add an AI reranking processor for Search API (owned by the AI module)
[4] 3581952 add free-form metadata bag on InputInterface; seed pre/post/streaming...
[7] fix(deps): update npm minor and patch
[8] Draft: Stage Canvas autosaves in a dedicated Workspace
[16] Issue #3586161: Add entity schema fields.
[18] Issue #3586304: Clean up CCC form and table accessibility cleanup
[21] Resolve "Drupal 10 compatibility" 2x
[22] Resolve "Drupal 10 compatibility" 1x