Repository navigation
desktop: Export session and Reveal in Explorer fail with "Desktop IPC handler failed" #50216
Description
Description
Desktop actions using the file/dialog channel (Export session, Reveal in File Explorer) consistently fail with "Desktop IPC handler failed" on OpenCode Desktop 2.0.11 / Windows 10.0.26200.9457. The background service is healthy (status OK, server log clean) and agent-channel file ops via PowerShell still work, so the failure is in the desktop client IPC. Tried service restart, killing background processes, reinstall, and PC reboot — same error.
Plugins
none
OpenCode version
v2.0.11 (Desktop, channel latest)
Steps to reproduce
- Open OpenCode Desktop with a workspace folder.
- Click session ... > Export.
- Observe export failure with "Desktop IPC handler failed".
- In Review tab, click Reveal in File Explorer.
- Observe request failure with "Desktop IPC handler failed".
Screenshot and/or share link
No response
Operating System
Windows 11
Terminal
No response
Activity
Shidokatotan commentedon Sep 21, 2026
Additional diagnostics (Desktop 2.0.11, Windows 11):
Reproduced again: Export session fails every time with the "Desktop IPC handler failed" toast, and no file is produced. Nothing is written to main.log, renderer.log, crash.log, or the server log at click time — the click-time failure is completely silent in logs.
However, the debug-log bundle captured a related startup failure. On fresh launch, the background service crashed at startup:
renderer.log (fatal renderer error):
"Desktop IPC handler failed", caused by "Server process exited with code 1"
Server log, same second:
cli process failed ... FileSystem.rename (....local\state\opencode\service.json..tmp) ... EPERM: operation not permitted
So serve --service died on an EPERM while renaming service.json. About 18s later a retry succeeded and the app became usable. The failed attempt left the stale .tmp file behind (I removed it manually).
Environment notes: official Desktop build from opencode.ai, install healthy, service healthy afterwards, tested with third-party AV protection paused (same result), no plugins. Server log otherwise clean apart from benign "worktree discovery failed" warnings (project folder is not a git repo).
So there seem to be two layers: (1) flaky service startup due to EPERM on service.json (logged, evidenced above), and (2) Export / Reveal-in-Explorer failing even with a healthy service (not logged anywhere I could find).
Hona commentedon Sep 22, 2026
The Export and Reveal in Explorer failures are the same bug as #50153: since 2.0.11 the renderer sent optional RPC fields as
undefined(FilesSaveFile.options.titlefor Export,FilesOpenPath.applicationfor Reveal), which the main process's JSON schema codec rejected before the handler ran. Fixed in #50599 (merged tov2as 8e62ad7); it lands in the next desktop release after 2.0.12.The startup
EPERMon renamingservice.jsonin your second comment is a separate problem in the background service. If it keeps happening after the next release, please open a dedicated issue for it with that server log excerpt so it does not get lost under this title.