This week’s AI contributor meeting coincided directly with the landmark launch day of WordPress 7.0. The team focused on tracking the core release timeline, stabilizing the freshly debuted version 1.0.0 of the AI plugin, resolving high-priority architectural questions for the Abilities API, and restructuring technical and operational frameworks for the upcoming 7.1 cycle.
Announcements & Timeline
- WordPress 7.0 Launch: The final core release processing was officially kicked off during the meeting hour. The core
trunkdevelopment branch is scheduled to reopen immediately following the final deployment to accept early alpha contributions for WordPress 7.1. - WordPress 7.1 Release: @jeffpaul noted that a formal call for the 7.1 major release squad will likely be published tomorrow on Make/Core.
- WordPress 7.0.1: to ensure immediate post-launch ecosystem feedback or technical regressions, a 7.0.1 release can be quickly shipped based on feedback seen by the Core team.
- AI Plugin 1.0.0 Released: The AI experimentation companion plugin successfully hit its 1.0.0 milestone yesterday. The launch was intentionally prioritized a day ahead of WordPress 7.0 to guarantee immediate stability and cross-version compatibility for early adopters interacting with core AI primitives.
WordCamp Europe (WCEU) Contributor Day Planning
The team consolidated logistical and strategic planning across two discussion blocks during the call to finalize their approach for the upcoming Contributor Day:
- Table Leadership: WordCamp Europe’s Core AI table will be co-led in person by @justlevine and @gziolo, with @gajendrasingh supporting asynchronously as the remote/online table lead. @justlevine confirmed his travel was successfully finalized, with generous corporate sponsorship provided by @rtcamp.
- Venue Preparation: @karmatosed advised the group to actively anticipate spotty venue Wi-Fi by emphasizing local development environments and offline-ready resources.
- User Research Orientation: The table will balance codebase contributions with beginner outreach. @karmatosed pointed out that many general attendees register for the AI table out of an interest to learn about or use AI rather than write core PHP. The team intends to use this captive audience for valuable user research to determine what specific AI tools and workflows the broader community actually wants.
- Low-Barrier Onboarding: @neel33 proposed running a structured 20-minute onboarding workshop at the start of the day. This session will walk non-technical contributors through the exact process of setting up local sandboxes, configuring API tokens, testing plugin experiments, and filing clear, actionable bug reports.
Abilities API Evolution
The group reviewed a dedicated list of milestone tickets to close out lingering architecture debates and chart a path forward for core primitives:
- Supporting Massive Scale (#21): The team discussed the long-term optimization required to safely register, filter, and surface hundreds or thousands of concurrent abilities within an active system without introducing database degradation.
- Action Item: @justlevine will advance this ticket by documenting emerging ecosystem trends and, if necessary, opening an expansive Trac ticket to coordinate broader core developer feedback.
- Ecosystem Alignment: @justlevine noted that third-party infrastructure has heavily coalesced around the “find tool” layout pattern. Organizing an experimental “find abilities” discovery workflow within the companion plugin is designated as the next technical milestone.
- Progressive Disclosure: As soon as the pending slug fragments PR safely merges into core trunk for 7.1, the team will begin prototyping multi-layered, complex nested abilities.
AI Plugin Updates & Experiments
Following the successful deployment of version 1.0.0, development focus officially shifts toward polishing experimental features targeted for the upcoming version 1.1.0 lifecycle, scheduled for release on Thursday, June 4.
- Displaying Additional AI Providers (#27): Discussion centered on defining strict, objective criteria for displaying third-party provider options on the core Connectors page. @jeffpaul suggested prioritizing free, open-source models that natively map to existing text or image generation primitives within the plugin. @justlevine noted that criteria could also be applied as checklist for how Core might add other default connectors to that screen.
- Experiment Initialization (#159): The team discussed refactoring how plugin experiments are booted, moving initialization logic away from explicit
register()methods toward standard, hook-basedinit()action routines. Sentiment leaned towards closing out this PR, but agreed for folks to comment on the PR to then decide next step. - Programmatic Encryption & Secrets Management (#560): @dkotter highlighted an active exploratory PR reviewing a standalone encryption utility built on prior implementation code from @ericmann (originally drafted from conversation within the core Two-Factor plugin Slack channel). The utility has zero UI footprint and focuses strictly on exposing standard backend
get_secretandset_secretmechanics to act as a proving ground for pitching a dedicated core Secrets Management API in 7.1.
Content Provenance (C2PA)
- Preserving Asset Manifests: The group evaluated three open PRs (#294, #302, #459) in the AI repository dealing with asset authenticity metadata. The current logic ensures that when an image containing an active C2PA manifest is uploaded, WordPress preserves the embedded provenance trail rather than silently discarding it during standard attachment optimization routines.
- Authority Systems: @jason_the_adams and @dkotter are examining the overarching authority structure of the system, seeking to clarify the technical and legal implications if WordPress.org eventually acts as an official content signing entity for open-source media verification. @jeffpaul previously provided a PDF from @originvault to @isotropic and @jason_the_adams to help guide WPORG in conforming to the C2PA spec.
Operational Clarity & Maintainership
- Defining Commit Boundaries: @jason_the_adams called for clearer operational boundaries regarding companion repository maintenance. Several primary provider plugins (OpenAI, Anthropic, Google) are experiencing review friction and risk stalling without explicitly named maintainers authorized to commit community PRs. @jason_the_adams aims for formalize where Automattic intends to lead/contribute in these areas.
- Project Prototyping Guardrails: @justlevine advised against launching ancillary side-projects without verifying active support teams first, noting that scattered repositories inadvertently pull focus and resources away from higher-priority core milestones.
Looking Ahead to 7.1 Strategy
- Landscape Re-survey: @jason_the_adams suggested taking a step back on upcoming calls to re-survey the broader AI space, acknowledging that model behavior and agent frameworks have shifted drastically since the team’s roadmap was first drafted a year ago. @jason_the_adams to disseminate any additional strategic guidance from @matt to the broader Core AI team.
- Meeting Layout Changes: Future contributor agendas will likely phase out rigid component headings (e.g., separating PHP vs. JS clients) in favor of a consolidated “Existing Work” overview paired with an expanded, open-floor strategy session.
- Core Streaming Support: Native streaming data support remains the top requested missing feature among early 7.0 testers. Building out deep streaming infrastructure is officially marked as a critical priority for the 7.1 cycle.
Next Steps
- Track feedback and bug reports following the WordPress 7.0 core launch.
- Review and leave feedback on the Connectors Visibility criteria ticket (#27).
- Update documentation and core tickets regarding Abilities structural scale (#21).
- Conduct code compatibility reviews on the experimental Secret Management encryption PR (#560).
Upcoming Meetings
- Folks are welcome to join on Wednesday’s at 1700 UTC via Google Meet with in-meeting notes captured in a Slack Canvas and then paired with Gemini meeting notes to help generate this meeting summary post. All team meetings are published to https://make.wordpress.org/meetings/#ai.
- Weekly AI Contributor Call (Google Meet): Wednesday, 27 May 2026.
- AI Team Office Hours (Slack): Thursday, 28 May 2026.
Props to @jeffpaul for pre-publish review.