[Bug] Ctrl+P is hijacked in ClawWork and should be customizable

[yankay]

What happened?

Pressing Ctrl+P inside ClawWork triggers ClawWork's internal shortcut handling (or does not produce the expected behavior), instead of the expected system or app behavior.

The same Ctrl+P shortcut works normally in other applications on the same machine, so this looks like a shortcut conflict inside ClawWork.

In practice, ClawWork appears to capture Ctrl+P unconditionally, without pass-through or user customization.

Steps to reproduce

1. Open ClawWork.
2. Press Ctrl+P.
3. Observe that ClawWork triggers its own internal behavior (or no expected behavior occurs).

What did you expect to happen?

Ctrl+P should not be unconditionally hijacked.

At minimum, ClawWork should:

• allow pass-through in appropriate contexts,
• let users remap or disable the default shortcut,
• and provide a visible hint when a shortcut conflict exists.

Affected area

Renderer UI

Environment

ClawWork version: 0.0.14
Build: 28
OS: macOS 26.2 (Build 25C56)
Architecture: arm64
Input method / keyboard layout: Tencent Input Method / Pinyin

Logs, screenshots, or recordings

N/A for now.

Additional context

This shortcut works as expected in other applications on the same machine, which suggests the conflict is specific to ClawWork rather than the OS or keyboard itself.

[github-actions]

Hi @yankay,
Thanks for opening an issue!
We will look into it as soon as possible.

Details

Instructions for interacting with me using comments are available here.
If you have questions or suggestions related to my behavior, please file an issue against the gh-ci-bot repository.

[samzong]

Hi @yankay — I can't find any Ctrl+P/Cmd+P handler in the codebase (renderer, Electron menu, and globalShortcut all checked). What did you expect it to do, and is Tencent Pinyin possibly intercepting it? Labeling needs-reproduction.