anomalyco / anomalyco/opencode

[BUG]: DeepSeek V4 Flash Free models.dev metadata shows 200K context instead of native 1M

Open Beginner friendly
#40,958 5 comments 1 reaction 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

DeepSeek V4 Flash Free on OpenCode Zen is capped at 200K context in models.dev metadata, while the model natively supports 1M context. This cap is not a hardware limitation — it's a metadata configuration issue that reduces the model's utility for long-context coding tasks.

This is NOT a duplicate of #27929 (which was closed with a client-side workaround). The issue here is that the server-side models.dev metadata still reports 200K as the default, which means every new user hits this limit unless they manually override it in their config.

Current state

The models.dev API returns:

{"limit": {"context": 200000, "output": 128000}}

This means:

  • Every user defaults to 200K context
  • Compression triggers at ~100K (50% of 200K)
  • Users must manually edit opencode.json to get the advertised 1M

Why this matters

DeepSeek V4 Flash is marketed as a 1M context model. The free tier should reflect this:

  • The model natively supports 1M (confirmed by DeepSeek's official model card)
  • Other free models on OpenCode (LongCat-2.0, Nemotron 3 Ultra) get their full 1M context
  • DeepSeek V4 Flash is the only one capped at 200K despite having the hardware capability

Request

Update the models.dev metadata for opencode/deepseek-v4-flash-free to reflect the full 1M context window (or at minimum, match what the paid tier offers).

Workaround (for now)

Users can add this to .config/opencode/opencode.json:

{
  "provider": {
    "opencode": {
      "models": {
        "deepseek-v4-flash-free": {
          "limit": {
            "context": 1048576,
            "output": 384000
          }
        }
      }
    }
  }
}

But this should not be necessary — the default should be 1M.

References

  • #27929: Previous issue (closed with workaround, not a real fix)
  • DeepSeek official model card: confirms 1M native context support
  • models.dev: currently reports 200K for the free tier

Environment

  • Provider: OpenCode Zen
  • Model: opencode/deepseek-v4-flash-free
  • models.dev reports: 200K context
  • Model natively supports: 1M context

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

Start by locating the models.dev metadata entry for opencode/deepseek-v4-flash-free and compare it with the paid tier and the cited model metadata. Update the context limit to 1048576, then verify that the models.dev API returns the intended value and that any relevant metadata checks pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.