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
Environment
- Provider: OpenCode Zen
- Model: opencode/deepseek-v4-flash-free
- models.dev reports: 200K context
- Model natively supports: 1M context
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:
opencode.jsonto get the advertised 1MWhy this matters
DeepSeek V4 Flash is marketed as a 1M context model. The free tier should reflect this:
Request
Update the models.dev metadata for
opencode/deepseek-v4-flash-freeto 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
opencode/deepseek-v4-flash-free#27929: Previous issue (closed with workaround, not a real fix)Environment