Open in Editor and Open in Finder shortcuts fail with a missing path argument

[SaKaNa-Y]

Describe the bug

Settings → Shortcuts lets me assign shortcuts to Open in Editor and Open in Finder, but pressing either shortcut does nothing visible. The browser console reports:

Error: The "paths[1]" argument must be of type string. Received undefined

Both commands failed consistently when repeated. Cmd+K still opens the command palette normally.

Reproduction

Reproduced with the repository's core playground:

1. Start the playground with pnpm -C playgrounds/core run dev after setting up the repository.
2. Open the playground in Chrome and authorize Vite DevTools.
3. Go to Settings → Shortcuts.
4. Assign Ctrl+Shift+E to Open in Editor and Ctrl+Shift+Y to Open in Finder.
5. Close the shortcut editor, focus the host page, and press each shortcut.

Neither action opens its target; both produce the error above. Each was repeated twice with the same result. This reproduction uses the existing playground rather than a separate reduced project.

Expected behavior

A shortcut offered in Settings should have a usable execution path. Could you clarify the intended behavior for these two commands: are they meant to support user-assigned shortcuts, and if so, where should the target path come from?

Code observations and ownership

The failing path crosses both repositories:

• Vite DevTools registers these two commands with a required path: string and showInPalette: false. Its RPC handlers resolve that path against the workspace root. The intended target of these Vite-specific commands belongs here.
• Devframe's @devframes/hub-ui owns the shortcut settings that offer these bindings and the keyboard dispatcher that calls execute(id) without arguments. Handling commands that require arguments may therefore need a change upstream in Devframe.

Filed here because this is reproducible in Vite DevTools with its built-in commands. Could you confirm the intended shortcut behavior and whether this issue should be transferred to devframes/devframe? These observations explain the missing-path error, but do not establish whether the intended resolution is to supply a target or restrict shortcut eligibility.

System Info

• macOS, Chrome 153
• Vite DevTools core playground; package version: 0.7.3
• @devframes/hub and @devframes/hub-ui: 0.9.18

Used Package Manager

pnpm

[SaKaNa-Y]

I noticed that assigning shortcuts to Open in Editor and Open in Finder doesn't work. Both commands require a path, but the shortcut handler calls them without one.

Are these commands intended to support keyboard shortcuts? If so, where should the target path come from? Or should they be excluded from shortcut settings?

I'd be happy to work on a fix for this issue.

[antfu]

I think maybe we should hide them from both the command palette and disallow binding shortcuts, as I don't think it has much meaning on calling them directly. Or do you have an expected use case?