anomalyco / anomalyco/opencode
[FEATURE]: DeepSeek: remove retired deepseek-chat / deepseek-reasoner from /models (models.dev#2979)
@rekram1-node is already working on this.
Since Aug 5, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
The /models list in opencode still shows four DeepSeek models:
deepseek/deepseek-chatdeepseek/deepseek-reasonerdeepseek/deepseek-v4-flashdeepseek/deepseek-v4-pro
DeepSeek discontinued deepseek-chat and deepseek-reasoner on 2026-07-24. They were never separate models — just aliases for deepseek-v4-flash modes (official changelog: https://api-docs.deepseek.com/updates). DeepSeek's official Models & Pricing page (https://api-docs.deepseek.com/quick_start/pricing) now lists only deepseek-v4-flash and deepseek-v4-pro, and the two stale entries return errors from the DeepSeek API.
Request: opencode should list only deepseek-v4-flash and deepseek-v4-pro under DeepSeek.
Since opencode's model list is fetched from the models.dev catalog (https://models.dev/api.json), the primary fix is a catalog change — removal requested at https://github.com/anomalyco/models.dev/issues/2979 (still open, unactioned). Until then, consider filtering or marking these entries deprecated client-side so /models stops surfacing dead aliases for every DeepSeek user.
Affected catalog files on dev:
providers/deepseek/models/deepseek-chat.tomlproviders/deepseek/models/deepseek-reasoner.tomlmodels/deepseek/deepseek-chat.tomlmodels/deepseek/deepseek-reasoner.toml
Benefits: removes dead, erroring entries from the model picker and shows users only the two real DeepSeek models.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.