As plugins start adding commands using the the Command Palette API, it would be nice if each command registered had the associated plugin name visible in the command. This way if there were competing commands (either between third-parties, or between a third-party and core) you would be able to identify which command you were looking for.

Not every command would utilize the plugin's branded icon (perhaps there isn't one even)—so we can't rely on just the visual.

It could be interesting if the plugin name was used as a fallback, but the command could register an alternate. There are considerations on both fronts, but I'm concerned about plugins that use extensive names (i.e. "Ninja Forms Contact Form – The Drag and Drop Form Builder for WordPress" — where the visible name should be "Ninja Forms".

Related to #53190 in theory. Perhaps the identification here—and type/category within that concept—are the same idea.

Visual