The openai custom api toggle does not toggle

Bug Reports
1

Describe the Bug

I am unable to use custom models because the openai toggle does not switch on when I toggle it. it says “are you sure you want to enable…”, I click “Enable…”, it thinks for a split second, and then nothing happens. Clicking the “verify” button also shows this meessage and then does nothing; not even an error message or anything.

the other api toggles work as expected.

Steps to Reproduce

just click the toggle or verify buttons under openai.

Expected Behavior

When I click the toggle, it should switch on/off states.
when I click verify, it should toggle on and then run a curl command to test api.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

version: 1.1.6
commit: 5b19bac7a947f54e4caa3eb7e4c5fbf832389850

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2

Hey, yeah, we’ve noticed this bug before. Have you tried restarting Cursor? I guess this happens after you switch from one API key to another?

3

I tried resarting it just now, but the problem persists.

2 Likes
4

I have encountered a similar issue. To understand what the error is, you need to click Help → Developer Tools, and usually, the error will be visible in the console. Alternatively, you can check the Network tab. Typically, this is due to an incorrect key, an incorrect API host, or CORS not being configured properly.

5

I’m running into this issue as well. Steps I’ve taken:

  • I’ve updated to the latest version of Cursor (Version: 1.1.6).
  • I’m using the same API key that worked previously.
  • I’ve hit the “Verify” button a few times and there’s no obvious error or confirmation. (A side request: Can we make the verify confirm in a more explicit way? It’s quite ambiguous when it finishes verifying.)
  • I’ve restarted and the issue still persists

Attempting to enable the openAI key will trigger the Verify API key flow and then fail. The toggle state stays in disabled.

6

This is still an issue for me and it’s costing me extra money.

Below is my cursor version. I thought upgrading to the latest version would help, but that doesn’t appear to have helped at all.

Version: 1.2.2
VSCode Version: 1.99.3
Commit: faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0
Date: 2025-07-07T06:08:52.104Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 23.0.0

I’m using MacOS Sonoma 14.0

I’ve restarted Cursor a few times. I cannot get my original openAI key to verify, which was working previously. I tried verifying with a made up API, and as expected, that didn’t verify. Side note, I would still like like a more useful verification feedback instead of it doing nothing on pass or fail. I created another API key on openAI and that new API key does not verify.

I am able to get Anthropic and Google’s API keys to verify fine and enable their models with no problem.

Can I get some help with this? When I look at the openAI billing dashboard, it appears to be more costly to go through Cursor than directly through my API key.

7

Ah-hah! I found another post with how to fix this. You have to enable chatGPT’s gpt-4o model, because that’s the model that’s used for verification.

Separately, perhaps it makes sense to auto-enable the model used for verification when people try to verify their openAI key instead of having things silently fail.