macOS Desktop: standard editing shortcuts (⌘V/⌘C/⌘X/⌘A) don't work

[Shixin000]

Summary

Official Desktop on macOS: standard editing shortcuts do nothing anywhere in the
app. ⌘V cannot paste into the chat composer or the API-key field, and ⌘C/⌘X/⌘A
are equally dead. Affects every text input, so pasting code or credentials is
impossible.

Reproduction

1. Launch the Desktop app (pnpm run dev:desktop, and see Notes re: packaged).
2. Copy any text from another application.
3. Focus any text field — the chat composer, or the onboarding API-key field.
4. Press ⌘V.

Current behavior

Nothing is inserted. No error, no dialog — the shortcut is silently ignored.
The same applies to ⌘C, ⌘X, and ⌘A.

Expected behavior

Standard macOS editing shortcuts work in every text field.

Environment

• macOS (Darwin 25.6.0), arm64
• Electron 44.0.0
• @deepseek-ai/dsh-desktop 0.1.5-rc.2

Notes

Likely cause: the application menu template in apps/desktop/src/main.ts:437
contains only { role: 'quit' }. On macOS, Electron dispatches the standard
editing accelerators through menu items; without role: 'editMenu' (or explicit
cut/copy/paste/selectAll roles), those accelerators are never registered, so ⌘V
is not delivered to the renderer. This block is unconditional — it is not gated
on development — so the packaged build is affected as well.
Minimal fix: add { role: 'editMenu' } to the template (viewMenu/windowMenu
would restore the other standard items).

[PerryLink]

Thanks for the precise report — we verified your diagnosis against the source, and it is correct.

apps/desktop/src/main.ts:437-450 is the app's only Menu.setApplicationMenu call. The template
contains exactly: Desktop Plugins… (accelerator CmdOrCtrl+,), Check for Updates…, a separator,
and { role: 'quit' }. There is no editMenu and no cut/copy/paste/selectAll role anywhere in the
app, and the block is unconditional (only the Plugins item's enabled flag depends on
development), so the packaged build is affected too.

On macOS, Electron registers the standard editing accelerators (⌘C/⌘V/⌘X/⌘A) through
application-menu roles; with no Edit-menu roles in the template those accelerators are never
registered, and the keys are dead in every text field — exactly what you measured.

Fix: add { role: 'editMenu' } to the template (plus viewMenu/windowMenu to restore the other
standard items). That is a small change we'll take as the fix direction — thanks for locating it.
Until then there is no in-app workaround we know of.

Unverified: this is static source verification; we haven't runtime-tested on a macOS machine here.