Skip to content

desktop: open in file manager fails with Desktop IPC handler failed #50632

Closed as not planned

Description

@Mitty-Guang

Summary

The desktop app's "open in file manager" action fails with the toast 请求失败 / Desktop IPC handler failed. Windows File Explorer never opens.

Environment

  • opencode version: 2.0.13 (desktop app; bundled opencode-cli 2.0.13)
  • OS: Windows 10.0.26200.9457 (win32 x64)
  • Terminal: Unavailable: not applicable (desktop app)
  • Shell: Unavailable: not applicable (desktop app)
  • Install/channel: latest (built-in updater reports "up-to-date")
  • Active plugins: none

Reproduction

  1. In the desktop app, trigger the "open in file manager" action on a file or folder.
  2. The toast 请求失败 / Desktop IPC handler failed appears; Explorer does not open.

Expected Behavior

Windows Explorer opens with the target file/folder selected.

Actual Behavior

Toast: 请求失败 / Desktop IPC handler failed. No window opens. Reproducible for both C:\Windows (ASCII) and paths with non-ASCII names.

Additional Context

  • Desktop logs (%APPDATA%\ai.opencode.desktop\logs\<timestamp>\{main,renderer,crash}.log) show a normal startup and no IPC exception around the failure time; renderer.log only contains ResizeObserver loop completed with undelivered notifications warnings.
  • main.log confirms: version 2.0.13, updater reports "Update for version 2.0.13 is not available", background service ready at http://127.0.0.1:49374.
  • Workaround that works: run explorer.exe <path> (or explorer /select,<file>) from a terminal/agent shell.
  • Related: clicking a folder in the app also fails separately (fs/read 500 Path is not a file) — filed as a separate issue.

Activity

  1. github-actions commented on Sep 22, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

  2. Mitty-Guang commented on Sep 22, 2026

    @Mitty-Guang
    Author

    Confirmed — this looks like the same root cause as #47722. I've added a Windows data point there.

    Environment for the record: Windows 11 (10.0.26200.9457), desktop 2.0.13 (bundled CLI 2.0.13); fails for both ASCII and non-ASCII paths; workaround is explorer.exe <path>.

    #46981 looks like a different platform/symptom (Linux, infinite loading), so #47722 seems to be the better match.

    Happy to close this as a duplicate of #47722.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions