DeepSeek provider: mark retired aliases deepseek-v4-flash and deepseek-v4-flash-vision-exp as status = deprecated #7726

Summary

The first-party deepseek provider currently exposes 4 models, but DeepSeek officially serves only 2: deepseek-flash and deepseek-v4-pro.

Per DeepSeek's own docs, deepseek-v4-flash and deepseek-v4-flash-vision-exp are retired legacy names: requests are still accepted, but the underlying models are offline and are served by DeepSeek-V4.1-Flash and billed at the Flash price.

This makes downstream clients (e.g. OpenCode) surface 4 selectable DeepSeek entries where only 2 are real, which is confusing.

Evidence

• https://api-docs.deepseek.com/quick_start/pricing
  • The model table lists only deepseek-flash and deepseek-v4-pro.
  • Footnote (1): the old names deepseek-v4-flash / deepseek-v4-flash-vision-exp are still callable, but the corresponding models are offline and requests are served by DeepSeek-V4.1-Flash, billed at the Flash price.

Request

Both alias files already carry the intended marker from the maintainers:

providers/deepseek/models/deepseek-v4-flash.toml

## mark as deprecated soon
# status = "deprecated"

providers/deepseek/models/deepseek-v4-flash-vision-exp.toml

## mark as deprecated soon
# status = "deprecated"

Please uncomment status = "deprecated" on both files (or otherwise hide them from default pickers) so retirees stop showing up as first-class models.

Validation

• Catalog/docs cross-checked on 2026-09-22.