WordPress 7.0 Beta 3 is out. The final release is set for April 9, 2026, so there is not much runway left. Beta 3 is usually the point where features that are already “good enough” get their last bit of polish, and it is also where the odd race condition turns up.
The release carries 148 updates: 70 in the Editor and 78 in Core. If you run a busy site, this is the build to put on staging and try to break on purpose. That goes double if you are shipping anything that talks to an AI provider next month.
Dynamic AI client connectors
The biggest change under the hood is how the WP AI Client Connectors screen handles providers. It used to be a static list. In Beta 3 the UI reads providers from the WP AI Client registry instead, so a custom integration for some smaller LLM can register itself and have its settings show up on that screen without you patching Core.
I wrote about testing the AI Connectors UI in Beta 2 a while back. Moving to a dynamic registry makes the architecture feel a lot more like the rest of WordPress: modular and driven by filters.
How to test the release safely
Do not run a beta on a production server. I have watched transients get mangled during a major version jump, and cleaning that up on a Friday night is miserable. Either install WordPress Beta Tester or point WP-CLI at a sandbox.
# Update your staging site to the latest beta
wp core update --version=7.0-beta3WordPress Playground works if you would rather stay in the browser, but it will not surface anything server side, such as an Nginx timeout on a slow AI request.
Stability and the April roadmap
There is a lot of refactoring going on in the Interactivity API and DataViews, which is part of why WordPress 7.0 changes everything for core developers. Most of what is left is aimed at the April 9 date, and a good share of it goes to Trac tickets that have been sitting open since the early 6.x releases.
If Beta 3 testing is eating your week, I can take it off your hands. I have been working with WordPress since the 4.x days.
What to check before you ship
Beta 3 has little you can demo. What it does have is an AI provider layer you can extend, plus 148 fixes reported during the earlier beta rounds. Read the official AI Client documentation for the current hooks and filters before your next release goes out.
