module Native Command — a Alt/⌥+K command palette for ProcessWire (admin and front-end)

[Roych]

Hi all,

You know the moment: you're browsing your own site, you spot a typo in a title, an event that already happened, a date that's wrong. And you sigh, because now it's admin → find the page → edit → scroll → save → go back. Five screens for one word.

So I built Native Command — a command palette for ProcessWire, like Spotlight/Raycast or the VS Code palette. Press Alt+K (⌥+K on Mac) on any page of your site, front-end or admin, type a couple of letters, hit Enter. Done.

What can it do?

Things with the page you're looking at: set any simple field (text, number, price, date, checkbox, options, page reference — yes, next friday 19:30 works), publish/unpublish, hide, rename, duplicate, add a child page, move it, trash it.

Undo. Everything. Every change shows a little toast with an Undo button. Your editors will love you. You'll sleep better.

Bulk actions with selectors. "Unpublish all events that already happened": bulk unpublish → template=event, event_date<today → untick the one you want to keep → Enter. You get a summary of what was done and skipped (and why) — and one Undo for the whole batch.

"Wait, who uses this page?" Page info shows who created/changed it, URLs in all languages, and which pages reference or link to it. Trash and Move warn you about it automatically, before you break something.

Search & jump to pages (title, ID, template or a selector), admin screens, templates, fields, modules and users. Every page shows its template and ID — click the ID to copy it.

And a few extras: system info and latest errors right in the palette, clear caches, refresh modules, add a field to a template, your own no-code shortcuts in the settings (New event | new /events/ event | editor), pins, dark mode, and ? for built-in help.

Is it safe to give to editors?

Yes — that was the whole point. Every command, page and field is checked against the user's permissions on the server, every time. Commands use CSRF, risky ones ask first, rich-text fields are never touched, user selectors can't sneak past access control, and changes can be logged. No tables, fields or templates are created — uninstall and it's gone.

For developers

Add your own commands from any module or ready.php — with arguments, page pickers, confirmations, results in the palette and undo:

 

php

$wire->addHookAfter('NativeCommand::registerCommands', function(HookEvent $e) {
    $e->object->addCommand('orders.open', [
        'title' => 'Open orders',
        'mutates' => false,
        'handler' => function() {
            return ['message' => wire('pages')->count('template=order, paid=0') . ' open orders'];
        },
    ]);
});

Extra screens:
  
  

Download

Works on any site, any profile, no dependencies. ProcessWire 3.0.200+, PHP 7.4+.

Download: NativeCommand.zip

Install, press Alt/⌥+K, type ?.
If you run into any problems or bugs, please let me know and if it saves you even one trip through the page tree, I'll call it a win. 🙂

Cheers

R
 

[diogo]

Uuuuh, I love this!

I love that you get the values of selector fields to pick from, when editing one. Icing on top of the cake would be if you can also edit page fields 🙂

PS: by the way, I had to switch to cmd+p because cmd+k was interfeering with the palette command from the Konkat theme (I added that one there, sorry! 😄)

[Roych]

Update: Native Command 1.0.2 🎉

Thanks for the feedback so far — here’s what’s new:

• Edit any field. Set field… is now Edit field… and covers every field on the page. Simple fields (text, numbers, dates, checkbox, toggle, options, page reference) are still edited right in the palette, with undo. Everything else (rich text, images, files, repeaters, matrix, combo, table, map, third-party fields) opens ProcessWire’s own editor in a modal, showing just that field. Save, and the page refreshes.
• Page reference fields now work with every setup: parent, template, selector (incl. page. context), custom code, or “any page” with site search.
• New default shortcut: Alt/⌥+K. Konkat uses Ctrl/⌘+K for its own search, so they no longer clash. Prefer Ctrl/⌘+K or ⌘P? Pick any combination in the module settings.

As always, if something doesn’t work as expected, let me know. 🙂