As is known to all, deepseek released a new open-source version v3.2 two days ago, with 685b model parameters. There has been a significant improvement in tool usage. We hope the cursor team can add it as soon as possible. Thank you.
Amusingly enough, the version labeled ‘DeepSeek V3.1’ on Cursor isn’t actually 3.1 at all — it’s just the minor revision DeepSeek-V3-0324, which they arbitrarily renamed to 3.1 and then never corrected until 3.2 came out.
DeepSeek-V3-0324 has a very short context window, making it unsuitable as a coding agent.
Cursor seems far more interested in keeping its margins than in hosting models that genuinely benefit users.
I’d really appreciate it if you could bring DeepSeek back as a native model — especially the latest DeepSeek V4 (including its thinking / agent-oriented variants).
V4 looks like a meaningful upgrade for tool use and agent workflows, so having it as a first-party model would make a big difference. BYOK / custom endpoints are possible, but they’re less stable and harder to rely on in Agent mode.
If native DeepSeek V4 support is something you can consider, that would mean a lot. Thank you for listening.