desktop: file/folder pickers always fail on Windows — request schema rejects undefined for optional options.title / options.extensions ("Desktop IPC handler failed") #50503

Description

Summary

In OpenCode Desktop 2.0.12 for Windows, opening the native file picker (Ctrl+U / attach button in chat, and folder picker) always fails with the toast "Solicitud fallida / Desktop IPC handler failed". The request never reaches dialog.showOpenDialog. Pasting images (Ctrl+V) and drag & drop work fine.

Root cause (confirmed by in-place instrumentation): the renderer builds the FilesOpenFilePicker request payload with fields set to undefined (title: t?.title, extensions: t?.extensions in openAttachmentPickerDialog), and the desktop IPC request schema requires every field to be present as string | null / array | null. Schema decoding rejects undefined/missing fields, so the request dies before the handler runs. Iteratively patching the payload to send null for title and extensions fixed the picker completely.

Environment

• opencode version: 2.0.12 (desktop, channel: latest, packaged: true)
• OS: Windows_NT 10.0.26200 (win32 x64)
• Terminal: Unavailable (desktop app)
• Shell: cmd.exe
• Install/channel: latest (auto-updater reports up-to-date)
• Active plugins: none

Reproduction

1. Launch OpenCode Desktop 2.0.12 on Windows.
2. Open a chat.
3. Press Ctrl+U (or the attach button) to add a file/image.

Expected Behavior

The native file dialog opens; chosen files are attached.

Actual Behavior

A toast appears: "Solicitud fallida / Desktop IPC handler failed". No dialog opens. The failure is completely silent in all logs (main.log, renderer.log, server log).

With an in-place patch that surfaces the underlying defect in the error message, the actual cause is revealed:

1. First: Expected string | null at ["options"]["title"]
2. After sending title: null, the next failure: Expected array | null at ["options"]["extensions"]
3. After sending null for both fields, the picker works.

The schema definitions (main bundle):

Rl = Qi(L)                                    // string | null
zl = oa({multiple: Qi(ta), title: Rl, defaultPath: Rl})
Bl = oa({multiple: Qi(ta), title: Rl, defaultPath: Rl, extensions: Qi($i(L))})
Gl = R(`FilesOpenFilePicker`, {payload: {options: Qi(Bl)}, ...})

The renderer caller (openAttachmentPickerDialog) sends:

e.openFilePicker({multiple: t?.multiple ?? !1, title: t?.title, defaultPath: t?.defaultPath, extensions: t?.extensions})

title and extensions end up as undefined (they are not required by the callers, e.g. the chat attachment flow passes only {defaultPath, multiple}), and the Effect RPC schema decode rejects them. Either the schema should accept undefined/optional fields, or the client should normalize undefined to null before sending.

A related secondary defect observed in earlier sessions: during first-launch onboarding, app.getPath('documents') failed with Failed to get 'documents' path on this machine (transient; resolved after OS restart), which also surfaced as the same "Desktop IPC handler failed" toast. Separately, the "Configuration file" button failed until ~/.config/opencode/opencode.json was created manually — it would be nicer if that button created/opened the default config instead of failing.

Additional Context

• Workarounds that always worked: paste images with Ctrl+V, drag & drop files into the chat window.
• The .NET common file dialog works fine on the same machine (tested via PowerShell), so the Windows shell is healthy — the bug is in the request/schema layer of the desktop app.
• The failure is completely silent: no log entries anywhere when it happens. Logging the IPC exit defect (console.error on the Die exit in the renderer) showed nothing because the error surfaced through a different path; surfacing the schema error text in the toast was what finally revealed the cause. A log line for failed desktop IPC requests would make such bugs much easier to diagnose.

Plugins

No response

OpenCode version

2.0.12

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response