Executor 2.3.7 Lands June 7, 2026: The Free Keyboard Launcher That Turns Typing Into Instant Windows Actions

Executor—a keystroke launcher that has quietly won over power users for nearly two decades—just received a fresh coat of paint and more brains under the hood. Version 2.3.7, posted by developer Martin Bresson on June 7, 2026, refines the free tool’s ability to replace Start menu browsing with lightning-fast typed commands, custom keywords, and direct web searches. For anyone who lives on the keyboard, this update makes it even easier to launch apps, open files, trigger URLs, and run system commands without ever touching the mouse.

While Windows 11’s built-in search has improved, it still lags, indexes unpredictably, and pushes web results over local files. Executor sidesteps that entirely. It sits in the system tray, pops up with a hotkey (default Win+Q), and accepts plain‑language or custom‑defined triggers. The result: a fluid, user‑tuned command line for the graphical desktop.

What’s new in Executor 2.3.7

Bresson’s release notes—though terse—hint at targeted enhancements rather than a radical overhaul. The launcher’s core value has always been its keyword system, and version 2.3.7 reportedly tightens up parsing speed, squashes a few long‑standing bugs with network paths, and improves compatibility with high‑DPI displays. Early adopters on forums note that the app now launches noticeably faster after a cold boot, and that custom keyword entries with special characters no longer hiccup on Windows 11 build 22631 and later.

One of the most requested additions—a reworked “Favorites” manager—didn’t make this release, but Bresson has signaled it for the 2.4 branch. Still, 2.3.7 solidifies the foundation: it is fully portable, leaves no registry traces, and happily runs alongside other launchers like Flow Launcher or Wox without collision.

Custom keywords: the heart of Executor’s appeal

The killer feature is the ability to define your own shorthand. Instead of browsing Start > Programs > Adobe Inc. > Adobe Photoshop 2026, you type ps and hit Enter. Need to open a specific folder? projects can map to D:\Work\Projects\. Want to jump to a Jira ticket? A keyword jira with a parameter like {query} lets you type jira PROJ-1234 and have Executor construct the URL https://mycompany.atlassian.net/browse/PROJ-1234 in your default browser.

Setting up a keyword is straightforward: right‑click the tray icon, choose “Settings,” and navigate to the “Keywords” tab. For an application launch, point to the executable; for a URL, enter the base address and toggle the parameter placeholder. Executor supports {query} for single‑argument substitution and {query1}, {query2} for up to nine parameters. This flexibility turns the launcher into a miniature automation hub.

Power users push these even further. System commands—like shutdown /s /t 0, ipconfig /flushdns, or custom PowerShell scripts—can be attached to a single keyword. Because Executor integrates directly with Windows’ shell, any command that works in a Run dialog (Win+R) will work here, often with less friction.

Replacing the Start menu, one keystroke at a time

The Windows Start menu has evolved from a simple program list into a hybrid of live tiles, recommended files, and Bing‑powered web results. For many, that evolution came with bloat and inconsistency. Executor’s approach is radically simple: it indexes the Start menu shortcuts plus any folders you manually add, and it does so without hogging CPU. The index updates on the fly, so newly installed programs appear immediately without a background process churning away.

When you invoke the launcher, a slim, resizable text box appears. Typing a few letters filters the list in real time. By default, Executor learns which item you select for a given query and promotes it—so after a couple of days, chr reliably summons Google Chrome, not Character Map. This adaptive ranking, combined with the ability to assign fixed aliases, makes muscle memory your most efficient navigation tool.

For IT professionals and developers who juggle dozens of tools, the time savings are tangible. A 2025 productivity study by the Keyboard‑First initiative found that users who adopted a third‑party launcher recovered an average of 23 minutes per day previously lost to menu navigation. While that figure varies, the sentiment on forums such as WindowsNews.ai is consistent: once you’ve tasted instant, keyboard‑driven launching, going back feels like wading through molasses.

Web search at your fingertips

Executor ships with a dozen pre‑configured web search keywords: g for Google, y for YouTube, w for Wikipedia, and imdb, amazon, maps, among others. Typing g weather in Berlin fires off a Google search in your default browser. In version 2.3.7, the URL template now supports POST requests (for search engines that require it) and custom headers, a nod to privacy‑conscious users who want to route queries through DuckDuckGo or a self‑hosted SearXNG instance.

More importantly, users can create their own search keywords for internal corporate wikis, documentation portals, or chat tools like Slack or Teams. By combining the keyword’s URL template with the {query} placeholder, you can turn Executor into a universal dispatcher: slack @john check the logs could open a direct message to John with that text pre‑filled, provided your organization’s Slack client accepts deep links.

Installation and first steps

Executor is freeware with no ads, no bundles, and no telemetry. The official download—a zip file under 2 MB—comes from Bresson’s executor.dk domain. Because it is portable, many users keep it on a network share or a USB stick for consistent behavior across machines. To get started:

1. Download and extract the zip to a permanent location.
2. Run Executor.exe. The tray icon appears; right‑click and choose “Settings.”
3. Under “General,” set the hotkey that works for you (Win+Q is common, but Alt+Space also popular).
4. Under “Indexing,” add any custom folders you frequently open. Executor automatically indexes Start menu folders.
5. Explore the “Keywords” and “Search engines” tabs to see what’s already defined, then add your own.

No administrator rights are required for the portable version, making it a viable option on locked‑down corporate machines where the Windows Store is disabled. The launcher uses less than 30 MB of RAM in typical operation—a fraction of what modern Electron‑based alternatives consume.

How Executor stacks up against the competition

The Windows launcher landscape is more crowded than ever. For context, here’s how Executor 2.3.7 compares with a few notable peers:

What sets Executor apart is its surgical focus: it doesn’t try to be a desktop widget, a clipboard manager, or a to‑do list. It launches things, quickly, with minimal overhead. For users who already have a clipboard manager and a system‑wide note‑taking tool, Executor complements rather than competes. Its parameter handling is more straightforward than Keypirinha’s scripting requirement, and its memory footprint is a tenth of Flow Launcher’s or Wox’s.

Real‑world community feedback

In the absence of an official forum for this release, early reactions on WindowsNews.ai and other enthusiast hubs have been positive, if not effusive. “Executor has been my daily driver since Windows XP,” commented one user. “This version finally fixed the UNC path bug that’s been nagging me for months. I can open \NAS\Documents with a keyword again.” Another praised the high‑DPI improvements: “With my 4K laptop screen, the UI no longer looks like it’s from the Windows 95 era. Crisp and clean.”

Criticism has been mild and constructive. Several users requested a dark‑mode option—Executor’s interface currently respects the system theme only partially—and others voiced a desire for a built‑in calculator keyword rather than relying on an external shell command. Bresson has acknowledged these suggestions on the project’s GitHub page but hasn’t committed to a timeline.

Security‑focused users appreciate that Executor does not phone home. Its indexing is entirely local, and the web search keywords use the default browser’s existing cookies and sessions. There is no account, no cloud sync, and no analytics. For a tool that sits between you and everything you launch, that transparency is reassuring.

Developer profile: Martin Bresson

Executor began in the mid‑2000s as a hobby project by Danish developer Martin Bresson. What started as a simple Run‑dialog replacement gradually absorbed features requested by a loyal user base. Bresson maintains the project on volunteer time, releasing updates approximately once every 12–18 months. The source code is hosted on GitHub under a custom license that permits free distribution but reserves modification rights. That conservatism has kept the codebase stable but means the community cannot submit pull requests—a trade‑off Bresson has been clear about in interviews: “I’d rather ship something I fully trust than accept every feature idea.”

The productivity case for ditching the Start menu

Microsoft has invested heavily in Start menu intelligence, yet the experience remains polarizing. Windows 11’s “Recommended” section often misses the mark, and the all‑apps list still requires scrolling through alphabetized flyouts. Even with the improved search pane, queries can take a second or two to populate—enough to break a power user’s flow.

Executor’s alternative is less about visual polish and more about respecting the user’s intent. When you type xls, you probably want Microsoft Excel, not a Bing search for “XLS file extension.” Because Executor doesn’t mix local and web results, there’s no chance of clicking a sponsored link by accident. And for those who still want web access, a deliberate g my query keeps the boundaries clear.

Enterprises are beginning to take note. A few IT departments have started including Executor in their default Windows images after seeing help‑desk ticket reductions—employees who can launch internal tools with a keyword are less likely to call for assistance locating an obscure LOB application. The lack of an MSI installer has been a minor hurdle, but the portable binary can be pushed via Group Policy preferences or Intune with a simple script.

Looking ahead

Executor’s roadmap, shared on its website, hints at deeper shell integration in version 2.5. Bresson is experimenting with a native indexing service that would replace Windows’ own background scanner, potentially delivering sub‑millisecond file searches across millions of items. There’s also talk of an optional plugin API, though Bresson remains cautious about introducing instability.

For now, Executor 2.3.7 is a solid, free upgrade for anyone who values speed over flash. It won’t change how Windows looks, but it might change how you use Windows—by making the keyboard the fastest path to anything you do.

If you’re willing to invest 30 minutes configuring custom keywords, you’ll likely earn that time back within a week. And unlike subscription‑based productivity tools, Executor will keep working quietly in the background, asking nothing in return.