You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
desktop: open in file manager fails with Desktop IPC handler failed #50632
In the desktop app, trigger the "open in file manager" action on a file or folder.
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.
This issue might be a duplicate of existing issues. Please check:
Desktop silently ignores failures when opening the default file manager #47722: Desktop silently ignores failures when opening the default file manager — the IPC open-path handler resolves successfully even when shell.openPath() returns an error string, which appears to be the underlying cause of the Desktop IPC handler failed toast you're seeing.
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.
Activity
github-actions commentedon Sep 22, 2026
This issue might be a duplicate of existing issues. Please check:
open-pathhandler resolves successfully even whenshell.openPath()returns an error string, which appears to be the underlying cause of theDesktop IPC handler failedtoast you're seeing.Mitty-Guang commentedon Sep 22, 2026
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.