WordPress 7.0 Beta 5 is on the staging servers, and the Command Palette has finally turned into something I reach for. Most of the coverage is about the release date, so I went through the Trac tickets instead to see what actually changed under the hood. The new entry point in the admin bar is the part that matters if you spend eight hours a day inside the dashboard.
The omnibar and ⌘K
The main technical addition in WordPress 7.0 Beta 5 is the keyboard-first workflow. Logged-in editors now get a Command Palette field in the upper admin bar. Press ⌘K on Mac or Ctrl+K on Windows and an overlay opens where you can navigate, design or run actions without touching the mouse. That is a direct answer to the Command Center feedback from the last few cycles.
My earlier write-up on WordPress 7.0 Beta 2 and AI Connectors makes my bias obvious: I like anything that cuts administrative friction. Still, with more than 101 updates and fixes landing since Beta 3, this build is bleeding edge. Keep it off production.
Extending the palette in WordPress 7.0 Beta 5
The Command Palette has a public API, so it is not restricted to Core actions. If your plugin has a settings page, register a command and let users jump straight to it. The feature is built in React, so you enqueue a script that talks to the wp.commands package.
// Enqueue this in your admin_enqueue_scripts hook
import { registerCommand } from '@wordpress/commands';
import { plus } from '@wordpress/icons';
registerCommand( {
name: 'bbioon-custom-action',
label: 'Open Theme Settings',
icon: plus,
callback: () => {
window.location.href = 'admin.php?page=bbioon-settings';
},
} );How to test the release safely
I have hit enough white screens to distrust browser-driven updates on a beta. Use WP-CLI instead, mainly because it will not time out halfway through a long update routine. On a staging environment, this command drops you into the beta stream:
wp core update --version=7.0-beta5If you run complex AI integrations in WordPress 7.0, review your transient logic. Beta 5 fixes several race conditions in how the block editor handles concurrent data updates. The closed ticket list on WordPress Trac is worth a scan to see whether your own bottlenecks were refactored.
If WordPress 7.0 Beta 5 testing is eating your dev hours, I can take it on. I have been working with WordPress since the 4.x days.
Where the beta stands
The finish line is April 9, 2026. Expect a couple of release candidates between now and then, mostly polishing the omnibar. Unlike the earlier betas, this one reads as feature complete, which puts us in the bug-hunting phase. Test your custom post types against the ⌘K search: a site with thousands of records surfaces indexing errors that never show up on a demo install.
