OpenAI API key being set disables ability to use Composer 1

[darink (darin)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I use Composer 1 and I have OPENAI_API_KEY set, I get a 403. I pay for cursor, have pro plan, like up to 50 additional usage, but I want to use my own OpenAI API key I get through company when I’ve used that up.

All other cursor features work fine—tab, cmdk, etc.. and this problem does not happen when only setting ANTHROPIC_API_KEY, only with OpenAI.

I should be able to use composer even if I use OpenAI models with my own keys .

Steps to Reproduce

Enable valid OpenAI API key, use it, then try to use Composer-1

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.77
VSCode Version: 1.99.3
Commit: ba90f2f88e4911312761abab9492c42442117cf0
Date: 2025-11-13T23:10:43.113Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[deanrie]

Hey, thanks for the report. This is a known bug and the team is already tracking it.

When an OpenAI API key is enabled (either a custom key or via the OPENAI_API_KEY environment variable), it’s mistakenly applied to all models, including subscription models like Composer. That’s why you’re seeing those 403 errors.

Workaround: turn off your OpenAI API key when using Composer, and turn it back on when you need OpenAI models. You can quickly toggle it with CMD+Shift+0.

There’s no ETA for a fix yet, but the team is working on it. Let me know if this workaround helps.

[darink (darin)]

hey, is the case with anthropic models too? I thought when I had OpenAI API key set, Anthropic models were also working under their own API keys .

thanks for the shortcut. very useful.

[deanrie]

Yes, at the moment this also doesn’t work with Anthropic keys. You need to disable all your API keys if you want to use models from your subscription.