anomalyco / anomalyco/opencode

OpenCode chat produces blank output after sending messages — happens with Free Models too

Open
#48,623 1 comment 0 reactions 1 assignee View on GitHub

@Brendonovich is already working on this.

Since Sep 12, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

I’m experiencing a persistent issue in OpenCode where chat requests are not producing any visible model response.

The problem occurs in both new chats and previously existing chats.

What happens
I open OpenCode and go to a new session or open an existing/previous conversation.
I type a message and send it.
The message appears to be sent.
OpenCode makes a sound/beep, but no model response is generated or displayed.
The output/response area remains completely blank.
There is no useful error message shown in the UI.
Scope of the problem

This is not limited to one conversation or one model.

I have reproduced the issue with:

New sessions
Existing/previous sessions
Free Models Router / free models
Multiple model attempts

For example, I sent a GitHub URL such as:

https://github.com/D4Vinci/Scrapling

but OpenCode does not produce any response.

Expected behavior

After sending a message, OpenCode should process the request and display the model response, or show a clear error explaining why the request failed.

Image

Actual behavior

The request appears to be sent, but the response is completely blank and nothing is generated.

The issue appears to affect the entire chat functionality rather than a specific conversation or model.

I have attached a screenshot showing the problem.

Please investigate whether this is related to the OpenCode UI, request handling, model/router integration, session state, or another underlying issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.