Desktop app: no assistant reply to any message (CLI works fine) #36061

Summary

In the OpenCode desktop app (Windows 11), sending a message never produces a reply. This happens even on a brand-new session with the very first message — so it is not related to a prior "Interrupted" state. The CLI works fine with the same provider on the same machine and project, so the issue appears to be desktop-app-specific.

Environment

• OpenCode Desktop app — Windows 11
• Provider/model: Big Pickle
• OpenCode CLI on the same machine/project/provider: works correctly

Steps to reproduce

1. Open the OpenCode desktop app.
2. Click + to create a brand-new session.
3. Type Hello and send it as the first message.
4. Wait.

Expected behavior

The assistant streams a reply (as the CLI does).

Actual behavior

No reply at all. The user message is displayed, but there is:

• no streamed/assistant output,
• no error message,
• no loading/spinner indicator.

Sending additional messages behaves the same way.

What I've ruled out

• Not caused by the "Interrupted" state — reproduces on a clean session's first message.
• Not a general provider/CLI/network problem — the CLI works fine with the same provider on the same machine and project.

Workaround / recovery

Closing the project and starting a new session restores normal behavior. This suggests the app can get into a stuck state where messages send but no reply is returned, rather than a persistent failure.

Diagnostic info I can provide if helpful

• Desktop app version + build number
• App log files
• Whether the provider request is actually being sent (devtools/network console)