Hello Cursor Support,
My custom DeepSeek integration was working normally before, but Cursor now rejects the model before the request reaches the DeepSeek API.
Environment:
- Operating system: Windows x64
- Cursor versions tested: 3.24.9 and 3.23.23
- Mode: Agent
- Custom model: deepseek-flash
- OpenAI-compatible base URL: https://api.deepseek.com
- Authentication: My own DeepSeek API key
- Request ID: 1403831d-cddf-4bc2-b3a3-3277d011e1a0
Error:
AI Model Not Found
Model name is not valid: "deepseek-flash"
Developer Tools shows that the error originates from Cursor's agent backend:
ActionRequiredError: AI Model Not Found Model name is not valid: "deepseek-flash"
at streamFromAgentBackend
The same error occurs in a new chat and after downgrading from Cursor 3.24.9 to 3.23.23. I removed and re-added the custom model, re-enabled my API key, confirmed the base URL, restarted Cursor, and tested again. The behavior did not change.
I also tested the legacy model identifier "deepseek-v4-flash", but Cursor rejected it with the same "Model name is not valid" error.
The current official DeepSeek API documentation lists "deepseek-flash" as a valid model identifier. The configured endpoint and API key previously worked in Cursor.
This appears to be server-side model validation because:
1. The error is produced by Cursor's streamFromAgentBackend.
2. It occurs before any request reaches the DeepSeek API.
3. Downgrading the desktop client does not change the behavior.
4. The same configuration worked previously.
There is also a separate Developer Tools warning:
[otel.error] writeInitialRequest — You can only call end() on a span once.
However, the blocking error is the model validation failure described above.
Could you please confirm:
1. Whether custom DeepSeek models are still supported in Cursor Agent.
2. Whether "deepseek-flash" is currently blocked by Cursor's server-side model catalog.
3. Whether this is a regression or an intentional restriction.
4. How I can restore my previously working BYOK DeepSeek configuration.
5. Whether another exact model identifier must now be used.
Please let me know if you need the full Developer Tools log or additional request IDs.
Thank you.
**Where does the bug appear (feature/product)?**
- [x] Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
**Describe the Bug**
A previously working DeepSeek BYOK configuration stopped working after updating Cursor.
When I select the custom DeepSeek model and send any message, Cursor immediately returns:
`Model name is not valid: “deepseek-flash”`
The same DeepSeek API key and model configuration worked normally before the Cursor update. Removing and re-adding the API key/model did not resolve the issue.
Cursor logs indicate that the error is returned through the agent backend during `streamFromAgentBackend` / `writeInitialRequest`, rather than being caused by the contents of the chat prompt.
I also downgraded Cursor, preserving my user data and configuration, but the same validation error remained. This suggests that the stored model configuration or server-side model validation may no longer accept the custom DeepSeek model identifier.
**Steps to Reproduce**
- Open Cursor on Windows.
- Open Cursor Settings and configure a DeepSeek API key using BYOK.
- Add or select the custom model with the identifier `deepseek-flash`.
- Open a new Agent chat.
- Select the DeepSeek model.
- Send any message.
- Cursor immediately returns: `Model name is not valid: “deepseek-flash”`.
The error also occurs in a completely new chat and is independent of the prompt contents.
**Expected Behavior**
Cursor should accept the configured DeepSeek BYOK model and send the request directly to the DeepSeek API, as it did before the update.
If `deepseek-flash` is no longer an accepted identifier, Cursor should either:
- preserve and migrate previously working custom model configurations;
- allow the current DeepSeek API model identifiers; or
- display the exact supported identifier and migration instructions instead of rejecting the request with a generic validation error.
**Screenshots / Screen Recordings**
I can attach:
- A screenshot showing `Model name is not valid: “deepseek-flash”`.
- Cursor Developer Tools logs containing the `streamFromAgentBackend` / `writeInitialRequest` error.
- A screenshot of the DeepSeek BYOK configuration with the API key redacted.
**Operating System**
- [x] Windows 10/11
Windows 11.
**Version Information**
```yaml
IDE:
Version: 3.24.9
VSCode Version: [paste the value from Cursor diagnostics if available]
Commit: [paste the commit value if available]
I also reproduced the same error after downgrading to Cursor 3.23.23 without deleting my user data or configuration.
For AI issues: which model did you use?
Custom BYOK model: deepseek-flash
Provider: DeepSeek
The model and API key worked before the Cursor update.
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
Additional Information
- The failure occurs in both existing and completely new chats.
- Changing the chat prompt does not affect the error.
- Removing and re-adding the DeepSeek API key/model did not fix it.
- Reinstalling/downgrading Cursor while preserving user data did not fix it.
- The API key must not be included in this public report.
- Cursor Developer Tools logs show the request failing during the agent backend model-validation path.
- This appears to be a model registry/BYOK validation issue rather than a DeepSeek API authentication failure.
- Please confirm the currently supported DeepSeek model identifiers for BYOK and whether custom OpenAI-compatible DeepSeek endpoints remain supported.
Does this stop you from using Cursor?
- Sometimes - I can sometimes use Cursor
Cursor itself opens and other models may remain available, but my configured DeepSeek BYOK workflow is completely blocked.