anomalyco / anomalyco/opencode

[BUG] All online models stuck in 'Build' mode, only local Ollama models work

Open
#38,509 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description
Describe the Bug

All online models (including built-in free models like DeepSeek V4 Flash Free) are stuck in the Build state and never transition into the think state. However, local models (Ollama) work perfectly fine.

Environment Info
  • OS: Arch Linux
  • Node.js Version: v22.23.1
  • npm Version: 12.0.1
  • OpenCode Installation: Installed via AUR (paru -S opencode-bin)
  • OpenCode Version: 1.18.4.r24.g92cede0
Troubleshooting Steps Already Taken

I have already performed the following troubleshooting steps, but the issue persists:

  1. Network: Tested API connectivity via curl -v https://api.opencode.ai/v1/models, and it returns successfully.
  2. Auth: Verified credentials using opencode auth list, which shows OpenCode Zen api is active (1 credential).
  3. Clean Reinstall: Completely uninstalled OpenCode, cleared all caches and configs (~/.local/share/opencode, ~/.config/opencode, ~/.cache/opencode), and reinstalled via paru.
  4. Dependencies: Confirmed fzf, ripgrep, and unzip are installed, and the working directory is a valid Git repository.
Expected Behavior

The model should transition from the Build state to the think state and start processing the prompt.

Additional Context
  • Local Ollama models are functioning correctly.
  • No obvious errors are shown in the TUI.
Plugins

not

OpenCode version

1.18.4.r24.g92cede0

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

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.

Research direction

The report names no files or tests. Start by reproducing the issue with an online model and a local Ollama model, then trace the TUI transition from Build to think and compare their model or provider paths. Done means online models leave Build and begin processing while local models continue to work.

Written by the indexing model from the issue text.

Assessment

Tech stack
ollama, typescript
Domain
ai
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.