WordPress AI Workspace concept shown as a site dashboard with a chat assistant and connected software tools WordPress AI Workspace concept shown as a site dashboard with a chat assistant and connected software tools

WordPress AI Workspace Plan Sets Up Plugin 1.6.0

WordPress AI contributors are targeting an in-dashboard AI Workspace for plugin 1.6.0, planned for the end of November. The proposal pairs a chat-based agent with work to share reusable WordPress abilities across projects.

WordPress AI contributors are planning a chat-based AI Workspace for plugin version 1.6.0, which is targeted for the end of November. For site owners and developers tracking WordPress AI Workspace, the key distinction is that this is a proposal in development, not a released feature: the team is still working through how the experience and its shared building blocks should fit together.

Short version: AI plugin 1.6.0 is expected to bring an initial chat-based agent into WordPress, using models from configured AI connectors. Contributors also want the release to use a shared Composer package for WordPress abilities. The target is the end of November, but the team has not described the workspace as finished or confirmed a release date.

WordPress AI Workspace is planned for plugin 1.6.0

In its November 11 AI contributor summary, the WordPress AI team described 1.6.0 as the last regularly scheduled major AI plugin release before WordPress 7.2. The workspace is a primary focus. It brings together ongoing work on a site agent and the Command Palette into a more unified experience inside WordPress.

The first version is expected to let a user interact with a chat-based agent within WordPress. It would use models supplied through AI connectors configured for the site. The summary does not name specific providers, promise a launch date beyond the end-of-month target, or describe a complete list of tasks the agent will be able to perform.

That distinction matters for anyone planning a workflow around it. The team is outlining a direction and continuing development, not announcing a ready-to-install release. Features discussed for an upcoming version can still change before they ship.

How the workspace differs from the WordPress 7.3 vision

The AI team draws a line between the initial workspace and its broader plans for WordPress 7.3. The first version is intended to support interactions that operate within WordPress itself. The longer-term 7.3 direction discussed by contributors involves connecting external agents and tools through the Model Context Protocol, or MCP.

In practical terms, these are related but different stages of work. A chat interface in the WordPress admin is the proposed near-term experience; connecting external agents and tools through MCP belongs to the wider roadmap. The summary does not say that 1.6.0 will deliver the full 7.3 plan.

A shared abilities package could reduce duplicated work

The other major piece is a proposed shared WordPress Abilities package. The idea is to maintain reusable abilities in one place, then let projects such as the AI plugin and MCP Adapter consume them as a Composer dependency rather than keeping separate implementations.

Contributors agreed to move ahead with placing the package in the WordPress GitHub organization. That is a decision to proceed with the approach, not confirmation that every design choice is settled. The repository name and other implementation details remain open, and the team still needs to define how abilities move from experiments toward stable functionality.

The proposal could also let projects such as WooCommerce use selected abilities without requiring the whole AI plugin. That may be useful to developers who want to adopt individual capabilities rather than take on another full plugin dependency. For now, it is an intended benefit of the package, not a reported outcome from a finished release.

Maintaining a shared package also raises ownership questions. Contributors identified the need to establish who reviews changes, manages releases and maintains the code over time. Two contributors volunteered to begin coordination and maintenance, with the team saying it wants to broaden maintainership rather than rely on a single person.

Open pull requests and WordPress 7.2 work

About a dozen abilities pull requests are open, according to the meeting summary. The team said relevant work could move into the new package, instead of delaying the 1.6.0 release. Further abilities could continue to be developed and released independently as the package and its integration process mature.

The same meeting covered WordPress 7.2 release readiness. Contributors encouraged more testing of the Secrets API, especially on multisite installations, and discussed developer notes for Abilities API functionality ahead of Release Candidate 1. They also requested feedback on a proposal for defining ability permissions. The concern raised was whether permissions can be listed without running permission callbacks; the summary says the proposed change could be reverted if feedback does not arrive in time.

That work gives the upcoming AI plugin release a broader technical context. The workspace is one visible part of the effort, while APIs, permissions and shared code affect how developers build and connect features. The meeting summary does not say that all these pieces will be completed in 1.6.0.

Dependency review and plugin discovery remain in progress

Contributors also discussed dependencies in the PHP AI Client before WordPress 7.2. They clarified that Guzzle is a development dependency, not a production dependency, but noted that production packages, including PSR-related dependencies, may still need review. The team agreed to check whether updates affect code shipped with WordPress 7.2 before deciding whether another client release or more review is needed.

Separately, an ability scanner developed after a WordCamp Contributor Day can identify registered abilities and save that information as plugin metadata. The WordPress Meta team has reviewed the implementation, but it needs more cleanup before moving forward. A related Trac ticket explores identifying plugins that use the PHP AI Client. These efforts could help people find plugins that support AI connectors or AI features, but neither discovery tool is described as complete.

What developers and site owners should do next

For now, treat AI Workspace and the shared abilities package as active development plans. Developers can follow the AI team’s updates and review its open proposals; site owners should wait for the 1.6.0 release and its documentation before making plans that depend on a particular feature being available.

The next useful checkpoint is the release itself. Compare its changelog with these plans to see what shipped, what remains experimental and whether the team updated the timing.

FAQ

When is WordPress AI plugin 1.6.0 expected?

The team is targeting the end of November 2026. That is a target reported in the November 11 contributor summary, not a confirmed release date.

What is the WordPress AI Workspace?

It is an evolving concept for a chat-based agent experience inside WordPress. The initial plan is for it to use models available through configured AI connectors and bring together site-agent and Command Palette work.

Will the AI Workspace connect external agents through MCP?

The summary separates the initial workspace from the broader WordPress 7.3 vision for connecting external agents and tools through MCP. It describes the first version as focused on interactions within WordPress itself.

Leave a Reply

Your email address will not be published. Required fields are marked *