anomalyco / anomalyco/opencode

Responses in OpenCode chat are either very choppy or none after 'Thought'

Open
#41,353 1 comment 0 reactions 1 assignee View on GitHub

@jlongster is already working on this.

Since Aug 9, 2026.

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

Description

Description

I am running OpenCode with Ollama + Qwen3.5:9b/256K token window in VS Code. What I found when I ran brainstorming sessions is that the chat responses in OpenCode are often either very choppy or nothing at all after ‘Thought’ was outputted. The Gemini suggested the reason that OpenCode combines with a massive system prompt overhead that stalls OpenCode that struggles CoT text streams. So, I am wondering what the best configuration and usage heuristics (e.g., model choice, etc) so that OpenCode can actually be decently usable for such token intensive use cases.

Plugins

No response

OpenCode version

1.18.10

Steps to reproduce
  1. Install BMAD method (npx bmad-method install) (Version: 6.10.0) with OpenCode selected.
  2. Install Ollama (Version: 0.32.5).
  3. Install qwen3.5-9b via Ollama.
  4. Increase Ollama qwen3.5-9b token window to 256k.
    • create Modelfile, with
      FROM qwen3.5:9b
      PARAMETER num_ctx 256000
    • run ollama create qwen3.5-9b-256k -f ./Modelfile
  5. Install OpenCode CLI (Version: 1.18.10).
  6. Launch VSCode (Version: 1.131.0).
  7. Open VSCode terminal, enter
    ollama launch opencode --model qwen3.5-9b-256k
  8. Enter the following prompt in the OpenCode (Build mode) chat box:
    bmad-agent-analyst , I prepared the project context in docs/project_context.md for you to have a brainstorming session.
  9. Observed the following interactions.
Screenshot and/or share link

No response

Operating System

Mac M5 Pro

Terminal

Windows VS Code Terminal

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.