WordPress 7.1 Beta 1 landed on July 15, 2026, and if you have been ignoring the Gutenberg changelogs because "it's just block stuff," this is the cycle where that stops working as a strategy. The final release is scheduled for August 19, timed with WordCamp US, and there are at least three changes in here that will affect how you build, test, and ship WordPress sites this year.
Let me walk through the ones worth your time.
The AI Client is becoming a real API
This is the headline, even if the official developer blog buries it mid-post. WordPress 7.1 ships with streaming and embeddings support in the AI Client, the abstraction layer that core introduced to let plugins talk to AI models without hardcoding vendor SDKs.
What this actually means: if you are building a plugin that calls OpenAI, Anthropic, or a local Ollama instance, you no longer need to bundle your own HTTP client and manage API keys in your own settings page. The AI Client handles the connection layer, and as of 7.1, it handles streaming responses and vector embeddings natively. Embeddings are the backbone of semantic search, content recommendations, and RAG-style features. Having a standard WordPress API for them means plugin authors can stop reinventing that wheel.
If you run a site that uses any kind of AI-powered search, content suggestion, or automated tagging, watch the plugin ecosystem closely over the next two months. The plugins that adopt the AI Client early will be the ones that are easiest to swap between providers later, which is exactly the kind of lock-in avoidance that makes long-term maintenance sane.
Responsive styling is finally testable
Responsive styling in the block editor has been a "coming soon" feature for what feels like two years. In 7.1, it is officially open for testing. The idea is straightforward: you can set different style values for different viewport sizes directly in the editor, without writing custom CSS or adding media query classes by hand.
If you have ever tried to explain to a client why their heading looks great on desktop and terrible on a phone, you understand why this matters. The block editor is becoming a tool where non-technical users can actually control responsive design without breaking things or calling you.
It is not done. There are rough edges. But if you build client sites and care about reducing back-and-forth after launch, install Gutenberg 23.5 and start testing now, while you can still file issues before the August release.
React 19 compatibility is coming whether you are ready or not
Gutenberg 23.4 shipped React 19 compatibility tooling, and 23.5 raises the minimum required WordPress version to 6.9. If you maintain a plugin or custom block that touches React internals, the compatibility shim is a temporary bridge, not a long-term solution.
Run your plugin's JavaScript through the React 19 compatibility checks this week. The most common breakage points are refs, context types, and removed deprecated lifecycle methods. The migration is usually small, but finding out about it from a user's bug report in September is worse than finding out now.
Other things worth knowing
WordPress Studio is now on Linux. If you develop on Ubuntu or Fedora, the local development tool is finally available. The Playground team also added remote access over WebRTC, so you can share a live WordPress-in-the-browser demo without deploying anything.
The admin bar is back in the post and site editors. It was removed when the block editor launched. Its absence has been a constant friction point, and 7.1 restores it.
Block Bindings expand to List Items and nested content. Custom field bindings now work inside list items and nested group blocks, which was a common request from anyone building data-driven templates.
Layout gets real fixed widths and auto-fit grids. The block editor's layout system adds actual fixed-width support and auto-fit grid behavior, making dashboard and grid layouts easier without custom CSS.
What to do right now
Beta 2 landed July 22, Beta 3 comes July 29, and Release Candidate 1 is August 5. If you run production WordPress sites, test your plugins with Gutenberg 23.5 on a staging site now. The React 19 compatibility layer is the most likely source of breakage, and catching it now is cheaper than catching it after August 19.
If you build custom themes, review the layout and responsive styling changes in theme.json. The new fixed-width and auto-fit grid options may conflict with custom CSS you wrote to work around the old limitations.
The full developer roundup is on the WordPress Developer Blog, covering additional changes including the Components API deprecation wave, the Icons API, Unicode email support, and performance work. Worth a read if any of those are relevant to your stack.