Hi Cursor Team,
I am experiencing an issue where configuring a custom API key for DeepSeek seems to break the native Cursor models.
Environment:
-
OS: Windows
-
Mode: Ask and Agent Mode
-
Cursor Version: Version 3.19.7
Steps to Reproduce:
-
I added my DeepSeek API key in
Settings > Models > API Keys. -
I enabled “Override OpenAI Base URL” and set it to
https://api.deepseek.com/v1. -
I verified my DeepSeek key is valid by successfully calling
https://api.deepseek.com/modelsvia curl. -
I manually added the model IDs
deepseek-flashanddeepseek-v4-pro. -
I selected a native Cursor model, specifically Grok 4.7 High Fast.
The Issue:
When I try to send a simple message (e.g., “hello”) using the native Grok 4.7 High Fast model, I receive the following error:
Provider Error
We’re having trouble finding the resource you requested. If the problem persists, please contact support.
Request ID:bad63ae2-f7e6-4cbb-b1cf-eb6e66e2e202
(You can also see the “Invalid API key” error when I first tried to use the DeepSeek models, but it seems the request is now just routing incorrectly.)
Questions:
It seems that adding a custom DeepSeek endpoint/key is somehow interfering with the routing of native Cursor models. Is this a known issue with the new API key configuration UI? How can I use my custom DeepSeek key without breaking the native Cursor models (like Grok)?
Thank you for your help!