Azure o1 model API isn't working, but the 4o model API is functional

Bug Report
1

I used to use the GPT-4o model, and it worked fine.
Yesterday, I tried the o1-mini model but got an invalid credential error. I already checked the deployment name and key.

image
image1440×372 17.1 KB

I tested the o1-mini endpoint with curl, and it worked fine. It also works in another chat app I’m using.

Here’s the info of cursor

Version: 0.42.2
VSCode Version: 1.93.1
Commit: c499aee5f16e67815c7dc795ff338dc8ab3e07f0
Date: 2024-10-12T05:39:54.471Z
Electron: 30.4.0
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.26100
1 Like
2

If I change to gpt-4o model, it works fine

image
image1400×344 15.6 KB

3

Did you get this resolved? I am still having this issue with the exact same behavior (4o works, o1-mini does not).

Thanks!

4

O1 does not work but GPT-4o works. Is there any timeline to fix this

1 Like
5

I’m encountering the same issue with the Azure o1 model API not working, even though the 4o model API is functional. Is there an existing ticket for this problem, and any update on when it might be resolved?

1 Like
6

Still experiencing problems with this! I definitely past the deployment name, e.g. ‘pleasework’, and if it’s o1-preview it doesn’t work, but if it’s gpt-4o it works

7

I sincerely ask if anyone even ever succeeded to use Cursor with Azure

8

Seeing the same thing on my side. I’m able to use gpt-4o fine, not able to use o1-preview. I’ll keep following this space.

9

Hey all, it may be that our implementation here isn’t up to scratch to be able to be used with O1, but I’ll pass this on to the team and check what’s going on behind the scenes!

4 Likes
10

thank you because some of us have access to o1, it’s on Azure due to unrelated reasons, and we feel like we are one step away from being able to achieve amazing results. But that step has to be taken on your side

1 Like
11

Please implement this. Many thanks!

3 Likes
12

Cursor already implemented 100 models, but if you just add this advanced one that is so important to us, that if one of your devs is Christian, I’ll pray for the team, but if they swing another way I may sacrifice them a goat.

13

What is the ETA on this ?
This is happening because cursor is not specifying correct azure api version in backend .
Azure O1 requires latest API version .
Its 10 mins Fix , please include this in next update.

3 Likes
14

i will donate my first born if someone fixes this.

1 Like
15

Thank you very much!
I’m not sure if this is the root cause, but I’d like to add my point in case it helps. Some parameters in the Azure o1 series API are different: max_completion_tokens has been added to support o1-preview and o1-mini models. The max_tokens parameter does not work with the o1 series models.
FYI Azure OpenAI Service API version lifecycle - Azure AI services | Microsoft Learn

16

Thanks for the information, I’ve passed this to the team to see if this helps in any way!

2 Likes
17

Same here. Very annoying given how much we’re being charged for o1 use in Cursor

1 Like
18

any updates? thanks!

19

Good day there! Is it true that the fix required to make o1 work is absolutely trivial?

20

We have this on our backlog of things to look at, but are currently dealing with the rollout of 0.45.x. We hope to look into this soon!