Hi there, Cursor Team!
I’d like to point out a naming inconsistency with the DeepSeek models to avoid user confusion.
- The model currently listed as “Deepseek V3.1” (~60K context) is officially named “DeepSeek V3 0324”, as “V3.1” was an incorrect community name for it.
- The actual “DeepSeek V3.1” was just released in August 2025. It has a 128K context length and has NOT yet been integrated into Cursor.
To fix this, could you please:
- Rename the existing V3.1 model to its correct name: “DeepSeek V3 0324”.
- Add the new “DeepSeek V3.1” (August 2025) model with 128K context length.
- Update these changes in both the application and on the website to ensure consistency.
Thanks!