What’s new for developers? (April 2026)  🔗 **Source:** [What’s new for developers? (April 2026)](https://developer.wordpress.org/news/2026/04/whats-new-for-developers-april-2026/#playground) > [!note]+ Document Notes > --- > tags: #wordpress #collaboration #ai #playground #gutenberg #real-time > author: Jonathan Bossenger > source: WordPress Developer Blog > reference: https://developer.wordpress.org/news/2026/04/whats-new-for-developers-april-2026/ > date created: 2026-04-10 09:00 > --- > # 🏷️ Title: What's new for developers? (April 2026) > ## 🧰 Action Inbox > - [H1] Update PHP minimum to 7.4+ before WordPress 7.0 release — compatibility requirement #wordpress > - [H1] Migrate classic meta boxes to register_post_meta() for RTC compatibility — development priority #collaboration > - [H2] Test AI Client and Connectors API with provider plugins — integration testing #ai > ## 🧭 Table of Contents > - [[#📝 Summary]] > - [[#📖 Main Content]] > - [[#🗒️ Notes]] > - [[#📚 References]] > - [[#🗣️ Paraphrase]] > - [[#📰 Newsletter]] > - [[#✅ Action Items]] > - [[#🧪 Hypotheses]] > - [[#📊 Methodology]] > - [[#❓ Questions]] > - [[#🔮 Future Research]] > - [[#💡 Implications]] > - [[#🧠 Learning Styles Assessment]] > - [[#📊 Accessibility Assessment]] > - [[#🌍 DEIB Assessment]] > - [[#✅ Logical Validity]] > - [[#🛡️ DARVO Analysis]] > - [[#🎯 Conclusion]] > ### 🔗 References > - [WordPress 7.0 Field Guide](https://make.wordpress.org/core) > - [Playground MCP Server](https://github.com/WordPress/wordpress-playground) > ## 📝 Summary > - WordPress 7.0 release delayed due to Real-Time Collaboration performance issues requiring database architecture changes > - Major new features include AI Client/Connectors API, Client-Side Abilities API, and WordPress Playground MCP server > - PHP 7.4 becomes new minimum requirement, dropping support for PHP 7.2 and 7.3 > - Extensive Gutenberg improvements spanning collaboration, theming, and developer experience > - Release schedule to be announced by April 22nd after architectural fixes > ## 📖 Main Content > WordPress 7.0 represents a significant milestone with Real-Time Collaboration as the flagship feature, but the release has encountered an unprecedented situation. After reaching Release Candidate status, the release returned to beta due to performance issues in the RTC database architecture that require fundamental fixes rather than patches. > The Real-Time Collaboration system uses Yjs as the underlying CRDT engine with HTTP polling for universal hosting compatibility. However, the current implementation stores sync data in post_meta on a special wp_sync_storage post type, which disables WordPress's persistent post query caches whenever a user has the editor open. The solution involves implementing a dedicated database table for collaboration data. > Two interconnected AI systems debut in WordPress 7.0: the WP AI Client provides a standardized PHP interface for communicating with AI services, while the Connectors API establishes credentials storage and provider selection as platform-level infrastructure. This abstraction layer allows provider switching through configuration rather than code rewrites. > The Client-Side Abilities API extends the PHP-based system introduced in WordPress 6.9, offering JavaScript counterparts through @wordpress/abilities and @wordpress/core-abilities packages. This enables browser agents and WebMCP integration with input/output schemas and permission callbacks. > ## 🗒️ Notes > #### ⏱️ [00:00](https://developer.wordpress.org/news/2026/04/whats-new-for-developers-april-2026/#highlights) — [H1] WordPress 7.0 Release Delay Announcement > - Key idea: Unprecedented return to beta after Release Candidate due to RTC performance issues > - Evidence: "Returning to beta status after entering the Release Candidate phase is unprecedented" > #### ⏱️ [02:30](https://developer.wordpress.org/news/2026/04/whats-new-for-developers-april-2026/#php-requirements) — [H1] PHP Version Requirements Update > - Key idea: WordPress 7.0 drops support for PHP 7.2 and 7.3, requiring minimum PHP 7.4 > - Evidence: "WordPress 7.0 will drop support for PHP 7.2 and 7.3. The new minimum will be PHP 7.4, with PHP 8.2+ recommended" > #### ⏱️ [05:15](https://developer.wordpress.org/news/2026/04/whats-new-for-developers-april-2026/#rtc-architecture) — [H1] Real-Time Collaboration Architecture Issues > - Key idea: Current RTC implementation disables WordPress post query caches during editor sessions > - Evidence: "disables WordPress's persistent post query caches whenever a user has the editor open" > #### ⏱️ [08:00](https://developer.wordpress.org/news/2026/04/whats-new-for-developers-april-2026/#ai-client) — [H1] AI Client Standardization Layer > - Key idea: WP AI Client provides unified interface for multiple AI service providers > - Evidence: "provides a single abstraction layer, so provider switching is a configuration change, not a code rewrite" > #### ⏱️ [10:45](https://developer.wordpress.org/news/2026/04/whats-new-for-developers-april-2026/#connectors-api) — [H2] Connectors API Provider Ecosystem > - Key idea: Community-built providers extend official OpenAI, Google, and Anthropic integrations > - Evidence: "community-built providers for OpenRouter, Ollama, and Mistral have been published" > #### ⏱️ [12:20](https://developer.wordpress.org/news/2026/04/whats-new-for-developers-april-2026/#abilities-api) — [H2] Client-Side Abilities API JavaScript Implementation > - Key idea: JavaScript counterpart to PHP Abilities API enables browser agents and WebMCP integration > - Evidence: "laying the groundwork for browser agents and WebMCP integration" > #### ⏱️ [15:10](https://developer.wordpress.org/news/2026/04/whats-new-for-developers-april-2026/#meta-boxes) — [H2] Classic Meta Box Compatibility Impact > - Key idea: Classic meta boxes disable collaboration mode, requiring migration to modern alternatives > - Evidence: "Classic meta boxes will disable collaboration mode for a post" > #### ⏱️ [17:30](https://developer.wordpress.org/news/2026/04/whats-new-for-developers-april-2026/#style-variations) — [H3] Style Variation Transform Previews > - Key idea: Live previews available for block style variations before applying changes > - Evidence: "users can now see a live preview of the variation before applying it" > #### ⏱️ [19:45](https://developer.wordpress.org/news/2026/04/whats-new-for-developers-april-2026/#waveform-player) — [H3] Playlist Block Audio Visualization > - Key idea: New waveform visualization using @arraypress/waveform-player library > - Evidence: "displays a visual representation of the audio file being listened to" > #### ⏱️ [22:00](https://developer.wordpress.org/news/2026/04/whats-new-for-developers-april-2026/#pattern-overrides) — [H2] Pattern Overrides for Custom Blocks > - Key idea: Synced patterns now support custom blocks with per-instance content editing > - Evidence: "create synced patterns that include your own custom blocks while still allowing per-instance content edits" > #### ⏱️ [24:15](https://developer.wordpress.org/news/2026/04/whats-new-for-developers-april-2026/#interactivity-api) — [H2] Interactivity API Navigation Changes > - Key idea: state.navigation deprecated in favor of watch() function and server-side state.url > - Evidence: "state.navigation is now deprecated. The new watch() function and server-side state.url population enables cleaner patterns" > #### ⏱️ [26:30](https://developer.wordpress.org/news/2026/04/whats-new-for-developers-april-2026/#pseudo-states) — [H3] Button Pseudo-State Styling in Global Styles > - Key idea: Visual editor for button hover, focus, and active states without custom CSS > - Evidence: "No more needing theme.json or custom CSS to style button states" > #### ⏱️ [28:45](https://developer.wordpress.org/news/2026/04/whats-new-for-developers-april-2026/#block-visibility) — [H3] Viewport-Based Block Visibility Controls > - Key idea: CSS-based device visibility controls replace DOM removal approach > - Evidence: "Crucially, this is implemented via CSS, not DOM removal" > #### ⏱️ [31:00](https://developer.wordpress.org/news/2026/04/whats-new-for-developers-april-2026/#playground-mcp) — [H1] WordPress Playground MCP Server Integration > - Key idea: Claude and Gemini CLI can control Playground instances via WebSocket for local development > - Evidence: "letting your AI agent read and write files, execute PHP, manage sites, and navigate pages — all locally" > #### ⏱️ [33:20](https://developer.wordpress.org/news/2026/04/whats-new-for-developers-april-2026/#build-tools) — [H3] @wordpress/build Tool Introduction > - Key idea: esbuild-based replacement for @wordpress/scripts with automatic PHP registration > - Evidence: "replaces the webpack and Babel pipeline with a significantly faster esbuild-based engine" > ## 📚 References > - [Real-Time Collaboration Dev Note](https://make.wordpress.org/core/2026/04/rtc-dev-note/) > - [AI Client Dev Note](https://make.wordpress.org/core/2026/04/ai-client-dev-note/) > - [Connectors API Dev Note](https://make.wordpress.org/core/2026/04/connectors-api-dev-note/) > - [WordPress Developer Blog](https://developer.wordpress.org/news/) > ## 🗣️ Paraphrase > - WordPress 7.0 faces an unprecedented release delay as Real-Time Collaboration's database architecture needs fundamental redesign to prevent performance degradation of WordPress's post query caching system > - New AI infrastructure introduces standardized interfaces for multiple service providers alongside centralized credential management, enabling seamless provider switching without code changes > - Extensive developer experience improvements span from modern build tooling with esbuild to enhanced block editor capabilities including live style previews and viewport-based visibility controls > ## 📰 Newsletter > WordPress 7.0 brings exciting developments despite the unprecedented release delay! The Real-Time Collaboration feature hit a performance snag requiring database architecture changes, but this demonstrates WordPress's commitment to shipping quality over hitting deadlines. > The AI Client and Connectors API represent a major leap forward for WordPress AI integration. Instead of each plugin rolling its own OpenAI or Anthropic integration, developers can now use a standardized interface that supports provider switching through simple configuration changes. > Don't miss the WordPress Playground MCP server - it lets Claude or Gemini control a full WordPress instance locally, opening incredible possibilities for AI-assisted plugin development and testing. > Action items: Update your sites to PHP 7.4+ and start planning classic meta box migrations to maintain RTC compatibility. > Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) > ## ✅ Action Items > #### WordPress > - Core: Implement dedicated database table for RTC collaboration data, resolve performance regression > - Core Performance: Profile and optimize post query cache interactions with RTC sync data > - Core AI: Finalize AI Client provider abstraction layer, expand Connectors API ecosystem > - Community: Publish RTC migration guides for classic meta box developers > - Documentation: Update PHP compatibility guides for 7.4+ requirement > - Plugins: Review classic meta box usage across Plugin Directory for RTC compatibility > - Themes: Document pseudo-state styling capabilities in Global Styles interface > - CLI: Add scaffolding commands for AI Client provider plugins > #### DevRel > - Developer advocacy: Create RTC migration workshops, AI Client demo presentations > - Education: Develop tutorials for Playground MCP server integration with AI tools > - Developer experience: Test @wordpress/build migration paths from existing toolchains > - Developer marketing: Promote new AI standardization capabilities to plugin ecosystem > - Community management: Coordinate feedback collection on RTC architecture changes > #### OSPO > - Software Inventory: Track AI Client provider plugin dependencies, licensing compliance > - Security Management: Review Connectors API credential storage patterns, encryption standards > - Developer Support: Provide migration consulting for PHP version updates > - Community Engagement: Support RTC performance testing across hosting environments > ## 🧪 Hypotheses > - The dedicated database table approach for RTC will resolve post query cache performance issues without degrading collaboration responsiveness > - Standardized AI Client interface will accelerate WordPress AI plugin development and reduce vendor lock-in > - Playground MCP server integration will enable new AI-assisted development workflows for WordPress > - PHP 7.4+ requirement will improve core performance while maintaining reasonable compatibility window > ### 📊 Methodology > - Performance benchmarking: Compare RTC database approaches under concurrent user loads > - Ecosystem analysis: Track AI provider plugin adoption rates and developer feedback > - Usage metrics: Monitor Playground MCP server integration patterns and AI workflow adoption > - Compatibility assessment: Survey hosting provider PHP version support and migration timelines > ### ❓ Questions > - How will the RTC database architecture changes affect hosting providers with custom caching layers? > - What security considerations arise from AI Client credential storage across different hosting environments? > - How can the WordPress ecosystem balance innovation pace with backward compatibility requirements? > ### 🔮 Future Research > - Multi-provider AI orchestration patterns beyond simple provider switching > - Real-time collaboration scaling limits across different database architectures > - Integration opportunities between Playground MCP and WordPress development tooling > ### 💡 Implications > - Practice: Developers need PHP 7.4+ testing environments and meta box migration strategies > - Policy: AI provider integration requires new credential management and privacy considerations > - Security: RTC introduces new attack surfaces through real-time data synchronization > - Education: Training materials needed for AI Client usage patterns and Playground MCP workflows > - Funding: RTC performance fixes may require additional development cycle resources > ### 🧠 Learning Styles Assessment > Reading level estimate: 12th grade (technical developer audience) > #### 👀 Visual learners > - Present: Code examples, architecture diagrams for RTC database changes > - Improve: Visual flowcharts for AI Client provider switching, RTC collaboration workflows > #### 🔊 Aural learners > - Present: No audio version currently available > - Improve: Podcast-style technical deep-dive, recorded developer Q&A sessions > #### 🗣️ Verbal learners > - Present: Clear technical definitions, API terminology explanations > - Improve: More analogies for complex concepts like CRDT engines and MCP servers > #### 🧩 Kinesthetic learners > - Present: Code snippets, migration examples, scaffolding commands > - Improve: Interactive tutorials for AI Client setup, hands-on RTC testing guides > #### 🧠 Logical learners > - Present: Step-by-step technical reasoning, decision trees for migration paths > - Improve: Performance comparison tables, compatibility matrices > #### 🧑‍🤝‍🧑 Social learners > - Present: Community feedback references, contributor acknowledgments > - Improve: Discussion forums for RTC testing, collaborative migration planning > #### 🧘‍♀️ Solitary learners > - Present: Comprehensive technical documentation, individual migration guides > - Improve: Self-assessment checklists, solo learning paths for new APIs > #### 🌿 Naturalistic learners > - Present: Limited environmental connections > - Improve: Sustainability impacts of AI Client usage, energy efficiency considerations > ### 📊 Accessibility Assessment > #### Screen reader semantics > - Present: Proper heading hierarchy, semantic HTML structure > - Improve: Enhanced alt text for code examples, ARIA labels for navigation sections > #### Keyboard navigation > - Present: Standard web navigation, accessible focus indicators > - Improve: Skip links for long technical content, keyboard shortcuts for code sections > #### Contrast and readability > - Present: Adequate contrast ratios, readable font sizing > - Improve: Enhanced contrast for code syntax highlighting, larger line heights > #### Text resizing and reflow > - Present: Responsive design supports 200% zoom > - Improve: Better code block wrapping at high zoom levels > #### Media and captions > - Present: No media content requiring captions > - Improve: Transcripts for future video tutorials > #### Forms and interactions > - Present: Basic form accessibility for comments > - Improve: Enhanced error messaging, clear form labeling > ### 🌍 DEIB Assessment > #### Cultural breadth > - Present: Global WordPress community context, international hosting considerations > - Improve: Multi-language code examples, regional hosting provider WordPress dashboard showing the new Connectors page Gutenberg 22.9 adds via block supports. Theme and block developers can now layer a gradient over a background image directly through the block editor’s design controls — useful for overlays, text readability treatments, and decorative effects without needing custom CSS. If your block registers `background` support, gradient options will be available alongside existing image controls. #### Playground ##### WordPress Playground MCP server As someone who’s always interested in WordPress AI news, this is one I’m genuinely excited about. [WordPress Playground now has an official MCP server](https://make.wordpress.org/playground/2026/03/17/connect-ai-coding-agents-to-wordpress-playground-with-mcp/) via the new `@wp-playground/mcp` package. One command wires up Claude Code or Gemini CLI to a browser-based Playground instance over WebSocket, letting your AI agent read and write files, execute PHP, manage sites, and navigate pages — all locally, without touching the WordPress admin. ``` claude mcp add --transport stdio --scope user wordpress-playground -- npx -y @wp-playground/mcp ``` The MCP server exposes tools across four areas: * **Site management:** `playground_get_website_url`, `playground_list_sites`, `playground_open_site`, `playground_rename_site`, `playground_save_site` * **Code execution:** `playground_execute_php`, `playground_request` * **Navigation:** `playground_navigate`, `playground_get_current_url`, `playground_get_site_info` * **Filesystem:** `playground_read_file`, `playground_write_file`, `playground_list_files`, `playground_mkdir`, `playground_delete_file`, and more Think plugin testing, live database debugging, and theme scaffolding driven entirely by conversation. #### Resources ##### WordPress 7.0 Dev Notes and Field Guide The full Field Guide will be published alongside the rescheduled release. In the meantime, the published dev notes are essential reading if you’re preparing your plugins or themes. Here’s the full list so far: * [PHP-only block registration](https://make.wordpress.org/core/2026/03/03/php-only-block-registration/) Keep an eye on [make.wordpress.org/core](https://make.wordpress.org/core) for additional dev notes and the updated release schedule as they’re published. ##### Developer Blog * If you’re currently using `@wordpress/scripts`, this one’s for you. JuanMa Garrido published [a detailed introduction to `@wordpress/build`](https://developer.wordpress.org/news/2026/04/wordpress-build-the-next-generation-of-wordpress-plugin-build-tooling/) on the Developer Blog. The new tool replaces the webpack and Babel pipeline with a significantly faster esbuild-based engine and automatically generates PHP registration files from `package.json`. The migration path for existing `@wordpress/scripts` users is designed to be low-friction. If you’re planning to update your plugin’s build tooling, that post is essential reading. Never want to miss an article again? [Subscribe to the WordPress Developer Blog](https://developer.wordpress.org/news/subscribe/)., What’s new for developers? (April 2026), developer.wordpress.org, 01kpxe0ybk760vkcpn9wyzr3tq.