Repository navigation
Keyboard shortcuts for plugin commands #5979
Replies: 3 comments
|
+1, with a concrete case: jumping to the next agent that needs attention. The sidebar already knows which agents are waiting (needs input / failed / ready to review), and plugins can reach that through A |
|
Same need from the agent-monitor side: multihost roster, graph and mission control (tracking in omercnet/paseo-plugins#365, interactive graph merged in omercnet/paseo-plugins#364, implementation in omercnet/paseo-plugins#424). It adds an Agent overview grid with every running or attention-needing agent across hosts, driven by digits once open. Today it takes Cmd+K, type, Enter to summon; the whole point is one keypress: glance, pick a number, land on the agent. +1 for unassigned-by-default rows in Settings that the user binds; a suggested default used only if free sounds right. Happy to help implement or test against the plugin. |

Uh oh!
There was an error while loading. Please reload this page.
What I'm trying to do
I use a few plugin views many times a day (a pull request list, a planner). I'd like a single key combo to open each one, the way built-in shortcuts open a new agent or workspace.
How I do it today
I register each view as a command center item (
client.addCommandCenterItem) and open it with: command center → type → Enter. That works but it's three steps every time.The only way to get one key is to add a
keydownlistener onwindowfrom the plugin's client contribution. That only works where there is a DOM (desktop and web, not mobile), clashes with Paseo's own shortcuts and focus scopes, doesn't appear in the shortcut list in Settings, and can't be rebound. From that root context there's also noopenPanel, onlyopenSurface.Where Paseo gets in the way
@getpaseo/pluginhas no shortcut, keybinding or accelerator API.packages/app/src/keyboard/): bindings for each action, focus scopes, a help search, and user overrides in Settings that can rebind or clear a shortcut. But the bindings are a fixed list of built-inKeyboardActionIds, so plugin commands can't be added to it.What a better workflow would look like
Let plugin command center items take part in the existing shortcut system:
addCommandCenterItem({ ..., shortcut: "mod+shift+p" }). Paseo only uses it if nothing else has that combo.onSelectwith the same context the command center would pass (soworkspaceandagentitems still getopenPanel), and does nothing when that context isn't available.All reactions