[SOLVED] How to use Deepseek in Cursor?

Deepseek V3 and R1 are supported in 0.45 and 0.44!

You can enable them in Settings > Models > turning on deepseek-r1 or deepseek-v3. We host these models in the US.

10 Likes

But when will it support the composer?

5 Likes

Yes when does that happen?

Will they be considered premium models or not?

I noticed that it’s super fast, how many billion parameters does it use?

Those answers have been already supplied several times in the forum. It uses the full model, its premium but doesnt count as fast request AFAIK.

How much parameters these models?

For anyone else who refuses to use the search button, its 671B parameters.

3 Likes

Any idea why it doesn’t seem as good as the version you get on the deepseek website?

See

Is the explanation here most likely correct?

1 Like


is it only supported in the US?

Is there a way to add Deepseek with my own API key? We’re running it in Azure and would like to use it instead of Deepseek API.

1 Like

Cursor does not use the Deepseek API. They use Fireworks for hosting Deepseek.

See Potential concern with Deepseek R1 - #2 by danperks

Yes, It is important!

Please add deepseek-v3.2-thinking to our model lineup.

It currently ranks 15th on the WebDev leaderboard while being by far the cheapest option, making it the best value for web work.

Cost of deepseek-v3.2-thinking is dirt cheap:

where is deepseek? Went to the settings and there is nothing related toDS

3 Likes

Yeah, I don’t see deepseek in the models, and deep-seek now just got even cheaper.

1 Like

Any chance to make Cursor compatible with DeepSeek?

So far, these two cannot work together, and DeepSeek is the best value for money offer on the market.

Hey, thanks for the request. Right now, DeepSeek isn’t in Cursor’s native model list. V3 and R1 used to be available, but you can’t find them in Settings > Models anymore.

You can technically connect DeepSeek using your own API key via Add Custom Model with an OpenAI-compatible endpoint, but there’s a catch. DeepSeek V4’s thinking mode requires returning reasoning_content after tool calls, and that can cause errors in the agent flow. Details and discussion here: Compatibility with DeepSeek model's design to return reasoning content after tool calls?

If you want native support back, the best move is to vote and leave a comment on the current feature request so the signal is in one place: Pls Add DeepSeek V3.2 There’s no ETA yet.