claude-code - 💡(How to fix) Fix macOS app: file context menu 'Open in → Finder' does nothing (silent, no error)

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

The Copy actions all work. Open in → Finder does nothing: no Finder window opens, no file is revealed, and no error is shown anywhere in the UI. It fails silently.

  • The failure is silent (no toast, no error dialog, no console-visible error from the user's side), which suggests the underlying error is being swallowed rather than surfaced.
RAW_BUFFERClick to expand / collapse

What happened

In the Claude Code macOS desktop app, right-clicking a file link in the conversation transcript shows a context menu with Copy path, Copy relative path, Copy filename, and Open in → Finder.

The Copy actions all work. Open in → Finder does nothing: no Finder window opens, no file is revealed, and no error is shown anywhere in the UI. It fails silently.

Expected

Selecting Open in → Finder should reveal/select the file in a Finder window (equivalent to open -R <path>).

Ideally the Open in submenu would also offer opening the file in other applications (e.g. the default app for the filetype, or a chosen editor), not just Finder.

Steps to reproduce

  1. In a session, have the assistant reference a file as a clickable link in its response.
  2. Right-click the file link to bring up the context menu.
  3. Hover Open in, then click Finder.
  4. Observe: nothing happens. Finder does not come forward and the file is not revealed.

Notes

  • Copy path / Copy relative path / Copy filename from the same menu work correctly, so the menu wiring and path resolution are fine; the failure is specifically in the shell-out to open Finder.
  • The failure is silent (no toast, no error dialog, no console-visible error from the user's side), which suggests the underlying error is being swallowed rather than surfaced.

Environment

  • Claude Code macOS desktop app
  • macOS: Darwin 25.3.0 (arm64)

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING