Skip to content

[BUG] Desktop model picker omits deepseek-flash (DeepSeek V4.1 Flash) although server API and CLI expose it #48420

Closed as not planned

Description

@nugunaga

Description

On the OpenCode desktop app (v1.18.30, Windows 11), the model picker does not list deepseek/deepseek-flash ("DeepSeek V4.1 Flash"), even though every other layer exposes it:

  • DeepSeek API serves it (GET https://api.deepseek.com/models)
  • models.dev registers it
  • the running server's GET /config/providers includes it
  • the CLI opencode models lists it

The picker only shows the 3 older entries:

  • DeepSeek V4 Flash (deepseek-v4-flash)
  • DeepSeek V4 Flash Vision Exp (deepseek-v4-flash-vision-exp)
  • DeepSeek V4 Pro (deepseek-v4-pro)

Environment

  • OpenCode desktop v1.18.30 (channel latest, @opencode-aidesktop)
  • CLI opencode --version → 1.18.30
  • Windows 11 (build 10.0.26200)
  • Provider: DeepSeek (official API, provider id deepseek)
  • Config opencode.json:
    { "$schema": "https://opencode.ai/config.json",
      "model": "deepseek/deepseek-flash",
      "small_model": "deepseek/deepseek-flash" }

Steps to reproduce

  1. Configure the DeepSeek provider (auth via /connect / opencode auth login).
  2. Note that deepseek-flash is the new model id for DeepSeek V4.1 Flash (released 2026-09-10; the provider currently also routes the legacy id deepseek-v4-flash to V4.1 Flash).
  3. Open the desktop model picker.

Expected

"DeepSeek V4.1 Flash" (deepseek/deepseek-flash) appears in the DeepSeek section of the picker.

Actual

Only 3 DeepSeek models appear; deepseek-flash is missing. New sessions fall back to the last-used model (deepseek-v4-flash), and config.model = deepseek/deepseek-flash is effectively ignored for the primary agent.

Evidence

1. Running server GET /config/providers returns (deepseek provider):

deepseek-v4-flash-vision-exp  ->  DeepSeek V4 Flash Vision Exp
deepseek-v4-flash             ->  DeepSeek V4 Flash
deepseek-v4-pro               ->  DeepSeek V4 Pro
deepseek-flash                ->  DeepSeek V4.1 Flash   <-- present on the server

2. Running server GET /config returns:

{"model":"deepseek/deepseek-flash","small_model":"deepseek/deepseek-flash", ...}

3. CLI lists it:

$ opencode models
deepseek/deepseek-flash
deepseek/deepseek-v4-flash
deepseek/deepseek-v4-flash-vision-exp
deepseek/deepseek-v4-pro

4. DeepSeek API GET /models returns:

{"object":"list","data":[{"id":"deepseek-flash",...},{"id":"deepseek-v4-pro",...}]}

5. Desktop GUI picker omits it (only V4 Flash / V4 Flash Vision Exp / V4 Pro shown).

Impact

Desktop users cannot select the new deepseek-flash (V4.1 Flash) alias. It is mostly cosmetic today because the provider routes deepseek-v4-flash to V4.1 Flash, but the new model id is unselectable from the GUI and config.model does not take effect for the primary agent.

Possible cause

The desktop picker appears to filter/caches the provider model list (e.g. a "recents" filter and/or a bundled/stale registry) rather than rendering the live server list, so newly added model ids are omitted even though the server exposes them.

Related issues

Activity

  1. jpike88 commented on Sep 23, 2026

    @jpike88

    @rekram1-node you're aware this problem exists.... right?

  2. thdxr commented on Oct 11, 2026

    @thdxr
    Member

    Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.

    — from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions