anomalyco / anomalyco/opencode

DeepSeek-v4-flash-free model missing from OpenCode's Zen provider dropdown despite existing in /zen/v1/models API

Open
#43,805 8 comments 0 reactions 1 assignee View on GitHub

@kommander is already working on this.

Since Aug 21, 2026.

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

Description

Description

The deepseek-v4-flash-free model is listed in the Zen API response at https://opencode.ai/zen/v1/models, and is correctly referenced in my opencode.json config ("model": "opencode/deepseek-v4-flash-free"), but it does not appear in the OpenCode TUI's model picker dropdown under the opencode (Zen) provider.

This model should be available for selection, as it exists in the API and is configured as an agent. All other Zen models (e.g., mimo-v2.5-free, nemotron-3-ultra-free) appear correctly in the dropdown, but deepseek-v4-flash-free is missing.

What happened?

When opening the model picker dropdown in OpenCode TUI and filtering by the opencode provider, deepseek-v4-flash-free is not listed, even though:

The Zen API returns it: {"id":"deepseek-v4-flash-free","object":"model","created":1787289055,"owned_by":"opencode"}
It is configured as the orchestrator model: "model": "opencode/deepseek-v4-flash-free"
Other Zen models appear correctly in the same dropdown

Plugins

None installed. Using default OpenCode plugins only.

OpenCode version

v1.18.19

Steps to reproduce
  1. Open OpenCode TUI
  2. Trigger model picker (typically ⌘P or via command palette)
  3. Filter by provider: opencode (Zen)
  4. Observe that deepseek-v4-flash-free is missing from the list
  5. Confirm model exists via API: curl https://opencode.ai/zen/v1/models returns {"id":"deepseek-v4-flash-free",...}
Screenshot and/or share link

N/A — this is a model listing issue, not a visual rendering bug. The model simply does not appear in the dropdown despite being valid in the API.

Operating System

Windows 11

Terminal

Windows 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.