[bug]: macOS desktop app — ⌘F does not open find-in-page
@prateekshourya29 is already working on this.
Since Apr 17, 2026.
- Dominant language
- TypeScript
- Stars
- 59.6k
- Forks
- 5.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 49
Description
Is there an existing issue for this?
- I have searched existing issues. Closest related is #8663, but that one is about the web app overriding browser shortcuts. This report is distinct: the macOS desktop app does not provide find-in-page at all.
Current behavior
In the Plane macOS desktop app, pressing ⌘F does not open a find-in-page overlay. There's no visible way to search for text within the currently displayed view (issue list, page content, etc.).
For context, every comparable Electron/Tauri-based desktop app — VS Code, Slack, Notion, Linear, 1Password, GitHub Desktop — implements ⌘F as find-in-page. In a browser this comes for free; in a desktop app it has to be wired up with the host framework's API (Electron's webContents.findInPage() for example). It seems to be missing here.
Expected behavior
Pressing ⌘F (or Ctrl+F on Windows/Linux) should open a find-in-page overlay that searches the currently visible content and scrolls to / highlights matches. This is the baseline OS-level expectation for any desktop app that displays scrollable text.
Steps to reproduce
- Open the Plane desktop app on macOS
- Navigate to any page with a reasonable amount of content (long issue list, a page with paragraphs of text, a thread with many comments)
- Press ⌘F
- Observe: nothing happens — no overlay, no visible way to search within the page
Environment
- App: Plane desktop app for macOS, version
2.0.0(build260325tah3zsnil) - OS: macOS
26.4 - Variant: Cloud
Related
- #8663 — the web-app equivalent, resolved by moving Plane's internal shortcut off ⌘F/Ctrl+F so the browser's native find could work. In a desktop app there's no host browser to fall back to, so the app itself has to implement find-in-page.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.