Skip to content

Conversation

@michaeljolley
Copy link
Contributor

@michaeljolley michaeljolley commented Oct 29, 2025

This is a draft for a reason

Warning

This is not fully baked. All features are there and work as expected but the way fallbacks are ranked or "checked" to be included in global results will change before final release.

Important

However, for extension developers, there is a breaking change for fallback items that you'll want to review and adjust your extensions accordingly. This release includes a new required string Id property for FallbackCommandItem. While your existing extensions will continue to work, without this Id being set, your fallbacks will not display and will not be rankable.
Here are the relevant changes to IFallbackCommandItem and FallbackCommandItem.
Before this is released, you will want to prepare your extension fallbacks.

As an example, we are naming our built-in extensions as:

  • Calculator extension provider Id: com.microsoft.cmdpal.builtin.calculator
  • Calculator extension fallback: com.microsoft.cmdpal.builtin.calculator.fallback

While the content of the Id isn't important, what is important is that it is unique to your extension and fallback to avoid conflicting with other extensions.

Now the good stuff:

What the heck does it do!?

The backstory

In PowerToys 0.95, we released performance improvements to Command Palette. One of the many ways we improved its speed is by no longer ranking fallback commands with other "top level" commands. Instead, all fallbacks would surface at the bottom of the results and be listed in the order they were registered with Command Palette. But this was only a temporary solution until the work included in this pull request was ready.

In reality, not all fallbacks were treated equally. We marked the calculator and run fallbacks as "special." Special fallbacks were ranked like top-level commands and allowed to surface to the top of the results.

The new "hotness"

This PR brings the power of fallback management back to the people. In the Command Palette settings, you, dear user, can specify what order you want fallbacks to display in at the bottom of the results. This keeps those fallbacks unranked by Command Palette but displays them in an order that makes sense for you. But keep in mind, these will still live at the bottom of search results.

But alas, we have also heard your cries that you'd like some fallbacks to be ranked by Command Palette and surface to the top of the results. So, this PR allows you to mark any fallback as "special." Special fallbacks are treated like "top level" commands and appear in the search result based on their title & description.

Screenshots/video

I'll update this PR with a video once the settings UI has been solidified. Posting what it looks like today would be misleading.

GitHub issue maintenance details

Closes #38312
Closes #38288
Closes #42524
Closes #41024
Closes #40351
Closes #41696

@michaeljolley michaeljolley added Don't merge - Hold for release Hold off on merging this PR, even if it's approved. Product-Command Palette Refers to the Command Palette utility labels Oct 29, 2025
private static readonly CompositeFormat PluginOpenURL = System.Text.CompositeFormat.Parse(Properties.Resources.plugin_open_url);
private static readonly CompositeFormat PluginOpenUrlInBrowser = System.Text.CompositeFormat.Parse(Properties.Resources.plugin_open_url_in_browser);

private const string _id = "com.microsoft.cmdpal.builtin.websearch.openurl.fallback";

Check failure

Code scanning / check-spelling

Unrecognized Spelling

[openurl](#security-tab) is not a recognized word. \(unrecognized-spelling\)
@jiripolasek
Copy link
Collaborator

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Don't merge - Hold for release Hold off on merging this PR, even if it's approved. Product-Command Palette Refers to the Command Palette utility

Projects

None yet

3 participants