Jeffrey Paul 6:11 pm on 6 February 2026
Tags: ,   

AI Contributor Weekly Summary – 28 January 2026

This week’s AI contributor meeting focused on progress toward a proposed WordPress AI Client merge for WordPress 7.0, contributor capacity ahead of the February 19 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 milestone, and a live demonstration of an AI-powered GatherPress workflow built on the Abilities APIAbilities API A core WordPress API (introduced in 6.9) that creates a central registry of capabilities, making WordPress functions discoverable and accessible to AI agents, automation tools, and developers. Transforms WordPress from isolated functions into a unified system. and WP AI Client. The group also discussed tradeoffs between different AI integration approaches and where contributors can most effectively help in the coming weeks.

WP AI Client and 7.0 Timeline

The group revisited the status of the WordPress AI Client and the urgency of moving the work forward ahead of the mid-February Beta 1 deadline.

  • @jeffpaul confirmed that the WP AI Client is being proposed for inclusion in WordPress 7.0, with the understanding that LLM providers will live outside of coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. as separate packages or plugins.
  • @justlevine emphasized the importance of shipping a strong technical implementation early to avoid unnecessary scrutiny and technical debt.
  • While a Make/Core proposal draft exists, the group agreed that publishing a concrete technical PR to wordpress-develop is the most important next step.
  • Contributors agreed to check in with @flixos90 and @jason_the_adams in the Core AI channel to identify immediate gaps where help is needed.

There was alignment that, while 7.0 remains the goal, deferring to 7.1 is acceptable if more iteration time is required.

GatherPress AI Assistant Demo

@jmarx75 shared a live demonstration of an AI assistant built into GatherPress, a WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ project intended to replace MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area.-style functionality for WordPress events.

The demo showcased:

  • Creating events and venues using natural language prompts
  • Date calculation handled via a dedicated abilityAbility A registered, self-documenting unit of WordPress functionality that can be discovered and invoked through multiple contexts (REST API, Command Palette, MCP). Includes authorization and input/output specifications.
  • Stateful conversations that allow follow-up updates (e.g., refining event descriptions)
  • Direct use of the Abilities API mapped to PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/index.php functions exposed via REST

@jmarx75 noted that the implementation currently prioritizes functionality over polish and highlighted areas for future improvement, including UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. refinement, link handling, and prompt cost optimization. The group agreed the demo was a strong real-world example of how the Abilities API and WP AI Client can be used to build embedded, task-focused AI experiences within WordPress.

WPAI Client vs. MCP AdapterMCP Adapter Translates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts. Discussion

A detailed discussion followed comparing approaches for building AI-powered workflows:

  • @raftaar1191 suggested using the MCP adapter with external AI tools to reduce implementation complexity.
  • @justlevine and others noted that while MCP can be useful in some scenarios, using the WP AI Client and Abilities API offers better control over context, multi-step workflows, and future compatibility with embedded or host-provided models.
  • @jmarx75 clarified that GatherPress requires AI functionality embedded directly in the WordPress admin experience, making the WP AI Client approach the best fit for current goals.

The group agreed there is no single “correct” approach, and that experimentation across both models is valuable as the ecosystem evolves.

Cost, Providers, and Future Flexibility

Cost and accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) considerations were also discussed:

  • @jmarx75 raised concerns about token costs for casual users and the complexity of managing APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. keys.
  • Contributors suggested using smaller or cheaper models where possible and noted that MCP-based approaches may be cost-effective for users on flat-rate subscriptions.
  • @jeffpaul reiterated that providerProvider An AI service offering models for generation, embeddings, or other capabilities (e.g., Anthropic, Google, OpenAI). integrations will not ship in core and will instead be distributed separately, allowing flexibility without coupling WordPress core to specific vendors, and that open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. and free models are ones he hopes to most strongly advocate for.

There was general agreement that the current direction keeps WordPress well-positioned for future developments such as embedded models or host-managed AI offerings.

Next steps

  • Contributors will ask @flixos90 and @jason_the_adams in the Core AI channel where immediate help is needed on the WP AI Client.
  • @jmarx75 will continue refining the GatherPress AI assistant and address feedback from the demo.
  • Contributors are encouraged to help push the WP AI Client technical PR forward to allow meaningful review ahead of the February 19 Beta 1 deadline.

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.

  • The next bi-weekly AI Team Chat SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ discussion is scheduled for 5 February 2026.
  • The next weekly AI Contributor weekly Google Meet video call is scheduled for 4 February 2026.

Props to @psykro for pre-publish review.

#core-ai, #summary

Jeffrey Paul 3:01 am on 4 February 2026
Tags: ,   

X-post: Proposal for merging WP AI Client into WordPress 7.0

X-comment from +make.wordpress.org/core: Comment on Proposal for merging WP AI Client into WordPress 7.0

Jeffrey Paul 1:27 am on 4 February 2026
Tags: , , ,   

Call for Testing: Exploring New AI Experiments

Over the past few weeks, we’ve been experimenting with a handful of AI-powered concepts in the AI Experiments pluginAI Experiments Plugin WordPress's AI laboratory bringing all building blocks together. Serves as both a user tool and developer reference implementation. First release (v0.1.0) includes Title Generation experiment.. These concepts are intentionally exploratory. Some are rough, some may not stick, and all of them need feedback from folks actually using WordPress in the real world.

This post is a Call for Testing, with less interest in “is this perfect?” and more interested in:

  • Does this feel useful or confusing?
  • Would you expect this to exist where it does?
  • What would you change about the UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. or flow?
  • Does it behave as expected in your testing?

Below you’ll find a set of user-facing experiments, developer-focused tools, and one hybrid feature that cuts across both. Each section includes a short description, steps to test and a screencast example, a WordPress Playground link to utilize for testing, and a link back to the PR for feedback.

Please test what you’re curious about. You don’t need to try everything.

User-Facing Experiments

These experiments focus on AI features that surface directly in the WordPress admin or content workflows.

Type Ahead Suggestions

This experiment explores AI-powered type-ahead suggestions while writing. The goal is to understand whether inline suggestions help with flow and clarity, or whether they feel distracting or overly prescriptive.

We’re especially interested in feedback on:

  • Does the timing of suggestions feel right?
  • Do suggestions feel helpful or noisy?
  • Where would you expect controls or settings for this to live?

How to test:

  1. Launch using this WordPress Playground link
  2. Open the WP Admin dashboard
  3. Navigate to Settings > AI Credentials and add an APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. key to one of the AI clients listed, then click Save Changes
  4. Navigate to Settings > AI Experiments, check Enable Experiments, click Save Changes, check Type-ahead Text, and click Save Changes
  5. Navigate to Posts > All Posts and either edit the Hello world! post or click Add Post to open the post editor
  6. Start typing content and observe type-ahead suggestions
  7. Press Tab to accept or Escape to dismiss suggestions

Screencast:

Share feedback / leave comments: https://github.com/WordPress/ai/pull/151

Comment Moderation Assistance

This experiment explores using AI to assist with comment moderation. Rather than fully automating decisions, the focus is on providing helpful context or signals to moderators.

We’re especially interested in feedback on:

  • How do you feel about the AI Reply and Analyze with AI functionality?
  • Does this feel like assistance or automation?
  • Is the information presented at the right moment?
  • What would increase or decrease trust here?

How to test:

  1. Launch using this WordPress Playground link
  2. Open the WP Admin dashboard
  3. Navigate to Settings > AI Credentials and add an API key to one of the AI clients listed, then click Save Changes
  4. Navigate to Settings > AI Experiments, check Enable Experiments, click Save Changes, check Comment Moderation, and click Save Changes
  5. Navigate to Posts > All Posts, view the Hello world! post, and leave some sample comments on the post
  6. Navigate to Comments and utilize the AI Reply row action on a sample comment, select a suggested reply to use, and then Reply to the comment
  7. Utilize the Analyze with AI option in the Bulk actions dropdown menu
  8. Review Sentiment and Toxicity scores for Comments

Screencast:

Share feedback / leave comments: https://github.com/WordPress/ai/pull/155

Markdown Feeds

This experiment looks at consuming and working with Markdown-based feeds using AI. The goal is to explore new content ingestion workflows and how AI might help interpret or transform structured text.

We’re especially interested in feedback on:

  • Does this unlock workflows you care about?
  • Is Markdown the right abstraction here?
  • What would you expect next if this were expanded?

How to test:

  1. Launch using this WordPress Playground link
  2. Open the WP Admin dashboard
  3. Navigate to Settings > AI Experiments, check Enable Experiments, click Save Changes, check Markdown Feeds, and click Save Changes
  4. Navigate to Posts > All Posts and view the Hello world! post
  5. Change the end of the URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org to /hello-world.md and confirm text/markdown output

Note additional testing options:

  • Visit /?feed=markdown and confirm text/markdown output
  • Request a post with Accept: text/markdown and confirm Markdown output
  • Optional: use the new section filters to inject custom fields into output: npm run test:php -- --filter Markdown_Feeds

Screencast:

Share feedback / leave comments: https://github.com/WordPress/ai/pull/194

Extended AI Providers

This experiment expands the set of available AI providers, making it easier to test and compare different models and services.

We’re especially interested in feedback on:

  • Is the providerProvider An AI service offering models for generation, embeddings, or other capabilities (e.g., Anthropic, Google, OpenAI). selection UX understandable?
  • Do the abstractions make sense from a user point of view?
  • What information would help you choose between providers?

How to test:

  1. Launch using this WordPress Playground link
  2. Open the WP Admin dashboard
  3. Navigate to Settings > AI Credentials and add an API key to one of the three default AI clients listed, then click Save Changes
  4. Navigate to Settings > AI Experiments, check Enable Experiments, click Save Changes, check Extended Providers, and click Save Changes
  5. Return to the Settings > AL Credentials screen and explore the additional nine providers and configuration options
  6. Add an API key for at least one cloud provider (e.g., Groq, DeepSeek) and verify it saves
  7. Try the same task across multiple providers

Screencast:

Share feedback / leave comments: https://github.com/WordPress/ai/pull/148

Developer Experience Experiments

These experiments focus on developers building with, extending, or debugging AI features in WordPress.

AI Playground

The AI Playground is a developer-focused space to experiment with prompts, providers, and responses without wiring everything into a full feature.

We’re especially interested in feedback on:

  • Does this feel useful during development?
  • What’s missing that would make this part of your AI configuration process?
  • Are there any missing features or elements that you expected to find based on you understanding of “AI Playground”?

How to test:

  1. Launch using this WordPress Playground link
  2. Open the WP Admin dashboard
  3. Navigate to Settings > AI Credentials and add an API key to one (or more) of the AI clients listed, then click Save Changes
  4. Navigate to Settings > AI Experiments, check Enable Experiments, click Save Changes, check AI Playground, and click Save Changes
  5. Navigate to Tools > AI Playground and test out different prompts, providers, models, capabilities, and options
  6. Observe outputs from different provider, model, and option configurations

Screencast:

Share feedback / leave comments: https://github.com/WordPress/ai/pull/140

MCP (Model Context Protocol) Integration

This experiment explores MCP (Model Context Protocol) support, aiming to improve how context is shared and managed across AI interactions.

We’re especially interested in feedback on:

  • Does the MCP integration function as you would expect?
  • Is this solving a real pain point for you?
  • What documentation or examples would help adoption?

How to test:

  1. Launch using this WordPress Playground link
  2. Open the WP Admin dashboard
  3. Navigate to Settings > AI Experiments, check Enable Experiments, click Save Changes, check MCP, and click Save Changes
  4. Navigate to the top level MCP menu item and view the MCP screen to ensure that Enable MCP and Enable Server are toggled on and that the server shows as 🟢 Running
  5. Toggle the Expose via MCP item for various abilities to test
  6. Use the Test connection feature in the Connection test section to verify endpoint
  7. Copy a Client configuration and test in Claude Desktop or Cursor

Screencast:

Share feedback / leave comments: https://github.com/WordPress/ai/pull/152

Hybrid Experiment

AI Request Logging

This experiment adds logging for AI requests (provider, model, tokens, duration, cost estimate) that can be viewed from the Admin Dashboard as well as configurable retention period and automatic cleanup to help with debugging, cost tracking, and usage analysis.

We’re especially interested in feedback on:

  • Is the level of detail appropriate?
  • Who do you think this is for: site owners, developers, or both?
  • How should this data be surfaced or stored?
  • How would you want to filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output., hide, or export this data?

How to test:

  1. Launch using this WordPress Playground link
  2. Open the WP Admin dashboard
  3. Navigate to Settings > AI Experiments, check Enable Experiments, click Save Changes, check AI Request Logging, and click Save Changes
  4. Enable other Experiments (and necessary, related AI Client Credentials via Settings > AI Credentials) and perform actions that trigger AI requests (e.g. Title Generation, ExcerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. Generation)
  5. Navigate to Settings > AI Request Logs and view the AI Request Logs screen showing requests, tokens, and other data
  6. Review logged requests and metadata
  7. Test filtering by provider, status, and date range
  8. Verify “Purge logs” clears all entries
  9. Disable the experiment and confirm no new logs appear

Screencast:

Share feedback / leave comments: https://github.com/WordPress/ai/pull/149

How to Give Feedback

Feedback directly on the PRs is ideal, but broad impressions are also valuable (e.g. as comments on this post, messages in #core-ai). You don’t need to review code to participate, high-level product, UX, and architectural feedback is just as valuable here. If you’re short on time, even answers to one or two of these questions help:

  • Would you use this if it shipped tomorrow?
  • What’s the first thing you’d change?
  • Where does this feel surprising, in a good or bad way?

These experiments are about learning in public. Your perspective can help us decide what to refine, what to pause, and what to drop entirely. Thanks for helping shape what AI in WordPress could become.

Props to @dkotter for helping with content for this post and @justlevine for pre-publish review.

#ai-experiments, #call-for-testing, #core-ai, #needs-testing

James LePage 10:33 pm on 3 February 2026  

Content Guidelines: A Gutenberg Experiment

A single place in WordPress to capture site-wide content standards and context, so publishing tools can manage content that stays on-brand and consistent.

Summary

We’d like to explore Content Guidelines as a GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ experiment. The goal is to give site owners a first-class place in WordPress to capture the rules and context that shape how content should be written, edited, and managed.

A Gutenberg experiment is well-suited for this kind of work:

  • It intersects with multiple editor surfaces (post editor, site editor, and potentially admin views)
  • It enables early feedback from pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. and host ecosystems before committing to a stable APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways., while allowing us to design interfaces that dogfood modern WordPress components, wordpress/build, and other elements
  • It de-risks future AI integrations in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. by establishing the right foundations now
  • It defines a new kind of site-level configuration that doesn’t have a clear precedent in WordPress

Gutenberg experiments let us validate whether this concept belongs in core, how it should be modeled, and where it should live in the admin experience before committing to a long-term API.

The initial PR is up at #75164 (we’ll continue to iterate there), and the tracking issue for broader discussion is at #75171.

Why this matters

Most sites already have content standards: voice and tone, structural rules, image guidance, accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) expectations, linking practices, and more. Today, those guidelines often live outside WordPress in documents, PDFs, wikis, or institutional knowledge. That makes them harder to find while writing and harder for any tool, human or automated, to apply consistently.

Content Guidelines isn’t an AI-only feature. It doesn’t depend on AI, but AI should depend on it. A unified store of guidelines makes standards discoverable, portable, and reusable, whether the person applying them is a writer, an editor, a plugin, or an AI assistant.

What Content Guidelines enables

Having a shared, structured store of guidelines creates compounding benefits over time – first for the people and tools already managing content, and increasingly as AI-assisted workflows become part of the publishing process.

A single source of truth for content standards. Today, editorial standards are scattered across wikis, PDFs, onboarding docs, and tribal knowledge. Content Guidelines gives them a canonical home inside WordPress, available at the moment they matter – during writing and editing, not after.

Consistency across authors and tools. On multi-author sites, keeping voice, structure, and formatting consistent is an ongoing challenge. When guidelines are part of the platform, every contributor and every tool works from the same expectations.

More steerable AI behavior. When AI-powered features can reference a site’s actual standards – voice and tone, preferred terminology, accessibility requirements, structural constraints – the results are site-specific rather than generic, with less need for repeated prompting or manual correction.

Guardrails for agents. As WordPress evolves to support and enable autonomous agents that act on behalf of a digital presence, (handling customer interactions, managing commerce workflows, moderating content) those agents need to understand the site’s voice, boundaries, and standards. Content Guidelines keeps public-facing agents aligned with a site’s brand and expectations, even without human review of every action.

A shared, portable foundation across the ecosystem. A consistent source of truth makes it easier for multiple features – whether core, host, or plugin – to behave coherently without creating conflicting rules across separate settings panels. With import and export, guidelines can move with a site, be reused across environments, or serve as a starting point for new sites.

What this experiment includes

The experiment focuses on establishing the foundation needed to make guidelines broadly useful:

  • A UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. for defining site-wide content guidelines and context
  • Support for content guidelines at a global and optionally at a more granular level
  • Storage that can evolve over time, including basic revision history
  • A way for tools to retrieve guidelines reliably

The initial emphasis is on capturing and retrieving guidelines. AI-driven experiences like generation, review, and enforcement, which exist in AI Experiments, can build on top of that shared foundation.

How to follow along and share feedback

If you’d like to track progress or contribute feedback and use cases, the tracking issue is the best place to start: #75171.

The most helpful feedback right now is practical:

  • What content standards would you want tools to consistently follow?
  • Where do those guidelines live today?
  • What schema and fields should we land on?
  • Which workflows matter most: drafting, editing, rewriting, translation, image generation, review?
  • What would make this immediately useful on day one?

Kudos to @matveb for reviewing this post.

James LePage 12:00 am on 1 February 2026
Tags:   

AI Guidelines for WordPress

AI tools are now part of how many people write code, tests, and documentation. To help contributors use them responsibly, we’ve published a first version of AI Guidelines in the Make WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. AI handbook.

AI Guidelines

These guidelines are intended to be practical and lightweight: they don’t ban AI tooling, but they do set clear expectations for quality, licensing, and transparency.

What’s in the guidelines

At a high level, the guide focuses on five core principles:

  • You are responsible for your contributions (AI can assist, but it isn’t a contributor).
  • Disclose meaningful AI assistance in your PR description and/or TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket comment.
  • License compatibility matters: contributions must remain compatible with GPLv2-or-later, including AI-assisted output.
  • Non-code assets count too (docs, screenshots, images, educational materials).
  • Quality over volume: avoid low-signal, unverified “AI slop”; reviewers may close or reject work that doesn’t meet the bar.

The document also includes specific guidance for AI-assisted code, tests/QA, documentation, issues/support, and reviewer expectations, plus a short FAQ (including common tools like GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ Copilot, Claude Code, OpenAI Codex, and ChatGPT).

Read it and share feedback

Please read the handbook page and leave feedback – especially from maintainers and frequent reviewers who are already handling AI-assisted contributions at scale.

We’re tracking follow-ups and next steps in the GitHub core-program issue here.

What happens next

  • We’ll x-post this to core meetings and request feedback/iteration.
  • We’ll work toward a more prominent “policy” landing page (not just a handbook entry), similar to how other projects have approached responsible AI guidance.

As with much in AI, this is a fast-moving space. These guidelines are intended to be living documentation, updated and iterated on as the project gains experience and as the broader landscape evolves. If you have questions, concerns, or proposals for changes, please start a discussion in the #core-ai WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ channel.

Resource: AI Guidelines (handbook)

#core-ai

Jeffrey Paul 3:57 pm on 27 January 2026
Tags: ,   

AI Contributor Weekly Summary – 21 January 2026

The formerly named “CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-AI Contributor Check-in” from 2025 reconvened today as the “AI Contributor weekly meeting” in 2026 as a weekly video chat for contributors to discuss progress and milestones across the projects maintained by the WordPress AI team. 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.

This week’s AI Contributor meeting focused on follow-through after the AI Experiments 0.2.0 release, progress on Abilities work targeting core consideration, and the need to tighten coordination ahead of the WordPress 7.0 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 milestone on February 19. The group also discussed review bandwidth, documentation gaps, and upcoming decision points for the broader AI community chat.

AI Experiments PluginAI Experiments Plugin WordPress's AI laboratory bringing all building blocks together. Serves as both a user tool and developer reference implementation. First release (v0.1.0) includes Title Generation experiment.

The AI Experiments plugin v0.2.0 was released earlier this week.

  • The release announcement post is ready and awaiting a final +1 before publishing.
  • The current iteration of the Abilities Explorer is included in v0.2.0.
  • Looking ahead to v0.3.0, the group discussed refactoring the Abilities Explorer to TypeScript and exploring tighter integration with Data Views and Forms.
  • @dkotter noted that several experiment UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. items planned for v0.3.0 are awaiting review feedback from @jason_the_adams.

There was shared agreement that the 0.2.0 cycle took longer than intended, and that improving release cadence and review velocity remains a priority.

Abilities Work

@jorgefilipecosta provided an update on Abilities work targeting WordPress core:

  • Feedback and reviews on the Settings are nearly complete, and the work is close to being ready for merge.
  • Feedback and reviews on the Core Post Management Abilities PR is still underway.
  • After wrapping that effort, @jorgefilipecosta plans to propose a follow-up PR to continue expanding the Abilities surface area.
  • There was continued discussion around structuring abilities in a more granular way, including per–post type abilities, to allow greater flexibility and extensibility.

The group also reaffirmed the importance of clearly positioning Abilities as part of the AI component in core, to ensure related tickets are visible to the AI team and triaged appropriately.

PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/index.php AI Client and WordPress AI Client

@jason_the_adams shared that the PHP AI Client v0.4.0 has been released.

Next steps include:

  • Introducing integration tests in the PHP AI Client to catch issues earlier, informed by recent bug reports.
  • Shifting focus to upcoming WordPress AI Client updates.
  • Continuing preparation for publishing the AI client merge proposal and associated PRs, to allow sufficient discussion within core ahead of the Beta 1 deadline.

There was consensus that these proposals need to land soon to avoid being blocked by the February 19 timeline.

MCP (Model Context Protocol)

@ovidiu-galatan shared updates on MCP-related work:

  • Several PRs are open on the MCP AdapterMCP Adapter Translates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts. to implement the PHP MCP schema.
  • While the work is progressing, review bandwidth remains the primary bottleneck.
  • Contributors were encouraged to help review where possible to move the adapter forward.

The group reiterated that the MCP Adapter is expected to remain a canonical pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party., separate from the WordPress AI Client being considered for core.

Tooling, Documentation, and Upcoming Decision Points

Additional topics discussed included:

  • WP Bench: @raftaar1191 successfully tested WP Bench using Ollama Cloud, noting that while results were poor compared to hosted providers, the tool functioned as expected. The group agreed this would be a good topic for the next SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/-based AI community chat.
  • Meeting timing: There is ongoing confusion around whether weekly and bi-weekly calls occur at 1600 or 1700 UTC. @jeffpaul will confirm and update the calendar to resolve this.
  • Documentation gaps: @jeffpaul committed to reviewing the AI component and TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. handbook pages to ensure Abilities are clearly documented as part of the AI component, helping core triagers route issues correctly.

Next steps

  • @jeffpaul will publish the AI Experiments v0.2.0 announcement post and outstanding meeting summaries.
  • @jorgefilipecosta will finalize testing on the Core Post Management Abilities PR, notify @justlevine when ready for another review pass, and prepare a follow-up abilities PR.
  • @jason_the_adams and @flixos90 will continue coordinating on AI client releases and the core merge proposal.
  • @jeffpaul will confirm and update the correct meeting times for weekly and bi-weekly calls.
  • Contributors are encouraged to review MCP Adapter PRs and help test available drafts.
  • WP Bench and the February 19 Beta 1 milestone will be key topics for the upcoming community Slack chat.

Upcoming meetings

Reminder that all team meetings are published to https://make.wordpress.org/meetings/#ai.

  • The next bi-weekly AI Team Chat Slack discussion is scheduled for 5 February 2026.
  • The next weekly AI Contributor weekly Google Meet video call is scheduled for 28 January 2026.

Props to @justlevine for pre-publish review.

#core-ai, #summary

Jeffrey Paul 3:55 pm on 27 January 2026
Tags: ,   

AI Contributor Weekly Summary – 14 January 2026

The formerly named “CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-AI Contributor Check-in” from 2025 reconvened today as the “AI Contributor weekly meeting” in 2026 as a weekly video chat for contributors to discuss progress and milestones across the projects maintained by the WordPress AI team. 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.

This week’s AI contributor meeting focused on wrapping up the AI Experiments plugin 0.2.0 milestone, unblocking progress on Abilities work, and continuing coordination toward potential AI client inclusion in WordPress 7.0. The group also discussed improving review velocity and establishing a more predictable release cadence going forward.

AI Experiments PluginAI Experiments Plugin WordPress's AI laboratory bringing all building blocks together. Serves as both a user tool and developer reference implementation. First release (v0.1.0) includes Title Generation experiment. (v0.2.0)

@jeffpaul and @dkotter reviewed the remaining items in the 0.2.0 milestone earlier this week. Several PRs have already been merged, with a small number of stragglers being wrapped up or deferred to 0.3.0.

  • @jeffpaul is preparing the 0.2.0 release with the goal of shipping imminently.
  • A Make/AI post announcing the release and highlighting new experiments is planned shortly after.
  • Once 0.2.0 ships, the team will move into the next milestone, including deferred items and additional targeted experiments.
  • There was agreement that release cadence needs to improve; @jeffpaul and @dkotter will likely establish a recurring UAT, merge, and release rhythm (potentially UAT bi-weekly, release monthly) to prevent future milestones from dragging on.

Abilities and Abilities Explorer

Abilities work remains an active area of focus, with several parallel threads:

  • The Abilities Explorer PR, originally authored by @karmatosed, is close to ready but has been stalled due to review bandwidth.
  • @justlevine has been leading updates but has been dealing with illness; @dkotter offered to review and test the Abilities Explorer once he finishes remaining 0.2.0 work.
  • @jorgefilipecosta shared a proposal and PR for Core Post Management Abilities, intended both as a concrete feature and as an example of how third-party plugins could implement richer, schema-driven abilities.
  • The group discussed versioning and deprecation strategies for abilities, with @jason_the_adams encouraging contributors to engage on the existing track ticket and align on a forward-compatible approach.

There was also discussion around polymorphic abilities versus post-type-specific abilities, with interest in a layered approach that supports both generic, low-level abilities and more specialized ones where appropriate.

PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/index.php AI Client and WordPress AI Client

@jason_the_adams shared updates on the AI client work:

  • The PHP AI client v0.4.0 is expected to ship soon, followed by a new release of the WordPress AI client.
  • @flixos90 will research and outline a proposal for bringing the WordPress AI client (and its PHP dependency) into core, potentially bundling the PHP client similarly to the Requests library.
  • The WordPress AI client will likely be broken into smaller, focused PRs for core (for example, prompt building and settings handled separately).
  • Streaming support will be removed from the PHP client for now due to technical and hosting constraints.
  • Providers will not ship in core initially; instead, they will live in separate plugins, with a “kill switch” filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. planned to allow sites to disable AI functionality entirely or conditionally.

@isotropic offered to draft the Make/Core proposal post to support the core inclusion effort and help manage review load.

MCP (Model Context Protocol)

@jason_the_adams shared updates on MCP-related work:

  • @ovidiu-galatan has opened a series of PRs updating the MCP adapterMCP Adapter Translates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts., including schema-to-PHP class generation.
  • Several PRs remain open and are in need of review to move the effort forward.

Next steps

  • @jeffpaul will finalize and ship the AI Experiments plugin 0.2.0 release and publish a Make/AI announcement post.
  • @dkotter will review and test the Abilities Explorer after finishing remaining 0.2.0 reviews.
  • @jason_the_adams will post an update on abilities versioning and deprecation and continue coordinating AI client releases with @flixos90.
  • @isotropic will draft the Make/Core proposal post for AI client inclusion.
  • Contributors are encouraged to help review MCP PRs and test the latest Experiments pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. ahead of upcoming core discussions.

Upcoming meetings

Reminder that all team meetings are published to https://make.wordpress.org/meetings/#ai.

  • The next bi-weekly AI Team Chat SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ discussion is scheduled for 22 January 2026.
  • The next weekly AI Contributor weekly Google Meet video call is scheduled for 22 January 2026.

Props to @justlevine for pre-publish review.

#core-ai, #summary

Shadi Sharaf 7:39 pm on 22 January 2026
Tags: ,   

AI Contributor Weekly Summary – 22 January 2026

The AI Contributor weekly meeting reconvened today (Slack archive) to discuss progress, upcoming milestones, and coordination efforts across the projects maintained by the WordPress AI team. This meeting focused on preparation for WordPress 7.0 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 and tooling improvements for the team.

WordPress 7.0 Beta 1 preparation and timelines

@jeffpaul opened the meeting by reminding the team that WordPress 7.0 Beta 1 is just four weeks away (February 19th). This timeline constraint was emphasized throughout the discussion as a key factor for planning and decision-making.

Key items identified for the 7.0 milestone:

  • WP AI Client: a PR or a set of PRs need to be prepared, paired with a merge proposal post on Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
  • Abilities APIAbilities API A core WordPress API (introduced in 6.9) that creates a central registry of capabilities, making WordPress functions discoverable and accessible to AI agents, automation tools, and developers. Transforms WordPress from isolated functions into a unified system.: The client-side JS counterpart is intended to ship as part of 7.0
  • Additional core abilities: @jorgefilipecosta expressed hope to include settings management and user management abilities, with post management abilities also under consideration
  • Versionless AbilityAbility A registered, self-documenting unit of WordPress functionality that can be discovered and invoked through multiple contexts (REST API, Command Palette, MCP). Includes authorization and input/output specifications. Deprecation: @justlevine advocated for including versionless deprecation and a querying APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. in 7.0, acknowledging the time constraints

Regarding GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ workflows, @jorgefilipecosta clarified that they remain in early exploratory stages and will not impact the AI team’s efforts. Once shipped, they will simply be another consumer of abilities, with no expected major impact on AI initiatives. The potential for hybrid abilities was acknowledged but remains on hold pending a concrete use case.

WP AI Client updates

@jason_the_adams provided an update on the WP AI Client roadmap:

  • Integrating PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/index.php AI Client v0.4.0 into the WP AI Client
  • Planning PHP AI Client v0.4.1 to address a bug before the 7.0 milestone
  • @flixos90 is exploring the best approach to include PHP AI Client in core, similar to how the Requests library is integrated
  • @flixos90 will circle back with details on the integration approach
  • @jason_the_adams mentioned a forthcoming PR that will add a filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to control user access to running AI prompts, allowing site administrators to limit access by user, context, and other criteria
  • @isotropic to write the merge proposal for the WP AI Client inclusion in WordPress 7.0.

WP Bench and benchmarking tooling

@jeffpaul introduced discussion around WP Bench, an AI benchmarking tool developed by the team. @jason_the_adams provided an overview:

  • WP Bench evaluates various language models against WordPress-specific challenges, providing metrics on model performance in terms of WordPress knowledge and code execution
  • The goal is to motivate AI providers to improve their models for WordPress contexts, while also helping AI consumers select the right model for specific WordPress tasks
  • The tool is written in Python, with dataset tests defined in JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. format for easy contribution
  • Contribution is welcome, particularly in building out additional tests and datasets

@johnbillion and @raftaar1191 explored the operational aspects:

  • @johnbillion asked whether WP Bench is running anywhere where results can be publicly viewed, or if it’s primarily a local-first tool; @shadyvb shared a test run for inspection
  • @raftaar1191 offered to update the WP Bench documentation to clarify that it can be tested locally, particularly with Ollama, and to ensure users understand how to run it on their local machines

Observability, tracing, and evaluation

Several contributors raised questions about observability and evaluation methodologies:

  • @justlevine asked whether there has been discussion about using WP Bench to evaluate changes to AGENTS.md or prompts in the AI Experiments pluginAI Experiments Plugin WordPress's AI laboratory bringing all building blocks together. Serves as both a user tool and developer reference implementation. First release (v0.1.0) includes Title Generation experiment.
  • @jorgefilipecosta suggested that WP Bench could be used to evaluate AGENTS.md changes by running benchmarks and measuring score improvements
  • @shadyvb inquired about existing plans for supporting observability and tracing with tools like LangSmith or LangFuse

The group acknowledged that datasets are currently very limited, and current benchmark scores should be taken with a grain of salt. There was general agreement on the value of moving beyond manual evaluation and anecdotal experience toward more systematic testing approaches.

@jason_the_adams noted that the PHP AI Client is experimenting with integration tests that run real prompts (https://github.com/WordPress/php-ai-client/pull/176), highlighting the difficulty of catching API edge cases through manual and unit testing alone. This work may have broader applications for the team’s testing strategy.

Given that integration tests require API keys, @jason_the_adams clarified that for now they are limiting execution to himself and @flixos90 running locally at their discretion before merging PRs or releasing, noting that there isn’t a precedent for WordPress storing API keys as GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ secrets for this type of automation.

Next steps

  • @flixos90 will explore and report back on the best approach to include PHP AI Client into core, similar to the Requests library pattern
  • @isotropic will write the WP AI Client merge proposal for Make/Core
  • @raftaar1191 will update WP Bench documentation to include guidance on local testing, particularly with Ollama
  • The team will continue inviting contributors to test the WP AI Client
  • Discussion on versionless Ability Deprecation should continue toward consensus on a solution

Upcoming meetings

Reminder that all team meetings are published to https://make.wordpress.org/meetings/#ai.

  • The next bi-weekly AI Team Chat SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ discussion is scheduled for 5 February 2026.
  • The next weekly AI Contributor Google Meet video call is scheduled for 28 January 2026.

Props to @jeffpaul for reviewing this post.

#core-ai, #summary

neillmcshea 6:58 pm on 21 January 2026
Tags: , , ,   

Core-AI Contributor Check-in: October 29th, 2025

Editor’s note (@jeffpaul): These notes were sitting in draft, and while dated do capture prior discussions, decisions, and other updates so I’m publishing this meeting summary (in a condensed format) for transparency purposes.

TLDR; The team met to review progress across the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. AI initiatives, primarily focusing on the integration of the Abilities APIAbilities API A core WordPress API (introduced in 6.9) that creates a central registry of capabilities, making WordPress functions discoverable and accessible to AI agents, automation tools, and developers. Transforms WordPress from isolated functions into a unified system. into WordPress core, the immediate feature development for the AI Experiments pluginAI Experiments Plugin WordPress's AI laboratory bringing all building blocks together. Serves as both a user tool and developer reference implementation. First release (v0.1.0) includes Title Generation experiment., and the strategic prioritization of the WordPress AI client. Key updates included reaffirming the Abilities API’s presence in the WordPress 6.9 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process., plans to ship an initial 0.1 version of the AI Experiments plugin with core functionality, and a concentrated effort to release a foundational version of the WordPress AI Client to unblock feature development.

Key Highlights

Abilities API in WordPress 6.9 Beta

The server-side Abilities API has successfully landed in the latest WordPress 6.9 Beta 2 release, with the team’s immediate focus shifting to encouraging extensive testing and iteration based on community feedback.

  • Development Homing: Future development and iteration of the APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. will happen within WordPress Core, and the original Abilities API repository is likely to be archived following the 6.9 release.
  • Client-Side Move: The JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com abilityAbility A registered, self-documenting unit of WordPress functionality that can be discovered and invoked through multiple contexts (REST API, Command Palette, MCP). Includes authorization and input/output specifications. registration (front-end component) did not make the core merge deadline and will be moved to the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ repository. It will be released as a standalone NPM package to allow developers to easily incorporate it into their projects.

AI Experiments Plugin Progress

The pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. is moving past the scaffolding phase and is nearing its first feature release, which is expected to prompt broader community testing.

  • First Feature Release Target: The team plans to ship a 0.1.0 release once the admin settings screen PR and the first experimental feature, title generation, are merged.
  • Post-Release Testing: The 0.1.0 release will be accompanied by a call for testing to ensure the plugin’s architecture is sound across varied WordPress environments before more experimental features are built.
  • Technical Cleanup: Verbose documentation PRs (some possibly AI-generated) were merged with a plan to simplify them later. GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ Actions for linting/coding standards and a playground link for PR testing were merged to streamline the development process.

WordPress AI Client Update

The team is focusing development resources on releasing the first version of the WordPress-specific client to support the new features being built.

  • PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/index.php AI Client Release: Version 0.2.0 of the core PHP AI client was released about a week and a half ago, including various fixes and enhancements.
  • WP AI Client Focus: The priority is now a rapid release of the WordPress AI Client (WP AI client) to prevent it from blocking the AI Experiments plugin development.
  • Initial Feature Set (0.1.0): The proposed WP AI client 0.1.0 release will include the WordPress-specific Prompt Builder, the credentials management settings screen, and the WordPress HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. client/transporter.
  • Server-Side Only MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia: The initial WP AI client release will only support LLM querying on the server side. The REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/ endpoint, which enables client-side querying, will be deferred to a subsequent release.

MCP AdapterMCP Adapter Translates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts. Milestones

Following a major refactor, the focus is on resolving immediate follow-up issues to unblock internal adoption.

  • Major Refactor Merged: The large Major Refactor PR was merged, moving the MCP Adapter into its 0.3.0 series.
  • Immediate Fixes: Small, subsequent PRs were opened to address remaining technical feedback, as the priority was to merge the large refactor and allow work on smaller, more manageable fixes.
  • Release Priority: The team plans to quickly review remaining issues and release version 0.3.0 immediately, as the older version (0.1.0) is now unusable due to changes in the shape of the abilities. The adapter is actively being used on internal Automattic projects, making a quick release essential.

#check-in, #core-ai, #meeting, #summary

neillmcshea 6:51 pm on 21 January 2026  

Core-AI Contributor Check-in: September 3rd, 2025

Editor’s note (@jeffpaul): These notes were sitting in draft, and while dated do capture prior discussions, decisions, and other updates so I’m publishing this meeting summary (in a condensed format) for transparency purposes.

Zoom Link: https://us02web.zoom.us/j/85296485830?pwd=u2QlmopcccfTu8zvLnUKLbg61kE4Ol.1

Announcements (5 min)

  1. A very successful Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ at WCUS 🎉
    1. Thank you @justlevine for keeping things lit remotely
  2. PHP AI Client SDKPHP AI Client SDK A platform-agnostic library providing unified access to LLMs and embedding models from any major AI provider. Developed collaboratively with the PHP community. The WordPress AI Client SDK is the WordPress-specific package that adds REST API endpoints, API key management, and integrations through `AI_Client::prompt()`. is now available in its first release: https://github.com/WordPress/php-ai-client/releases/tag/0.1.0

Progress this week (5 min)

  1. Update to the handbook:
    1. https://make.wordpress.org/ai/handbook/contributing/
    2. https://make.wordpress.org/ai/handbook/resources-and-links/
    3. https://make.wordpress.org/ai/handbook/get-involved/
    4. https://make.wordpress.org/ai/handbook/contributing/project-management/ (WIP)

Questions/Decision points (15 min)

  1. New format for Weekly Check in review proposal Based on comments in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ and discussions at WCUS:
    1. Focus on updates from each of the projects (Project Facilitator + Lead)
    2. Review next Milestone – and tasks to support that milestone
    3. Blockers and Opportunities
  2. From @justlevine: Review mcp-adapter status and next steps.
    1. Align on immediate fixes and workflows.
    2. Update v0.1.0 release notes to prevent user confusion.
  3. Badges for CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. AI – For now contributors need to request themselves as per the instruction noted here. @jeffpaul working on being able to add link himself.
  4. Reminder From @karmatosed: As we fix roadmaps, let’s also reflect those in the projects. We will do that but I want to ensure they get logged into traceable formats that can take action also.