Ask mode with my own API Key required Pro Subscription

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I was using ask mode with a override OpenAI Base URL and my own API Key (No matter what model I used), but still got a message saying “Agent and edit rely on custom models that require a paid subscription. Please upgrade to a paid subscription or disable API Keys". It worked well just a few weeks ago. Why is this happening? Thank you.

Steps to Reproduce

Open Cursor’s agent chat tab, switch to ask mode and a custom model (with a override OpenAI Base URL and the corresponding API Key. Any model would get the same result), type into some simple questions or greetings and would only get error message requiring pro subscription.

Expected Behavior

The same procedure used to get normal answer from the LLM and would never require pro subscription.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 2.4.23 (user setup)
VSCode Version: 1.105.1
Commit: 379934e04d2b3290cf7aefa14560f942e4212920
Date: 2026-01-29T21:24:23.350Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26100

Additional Information

Error messages in dev mode:

workbench.desktop.main.js:34040 [composer] Error in AI response _je: Cursor Subscription Required Agent and Edit rely on custom models that require a paid subscription. Please upgrade to a paid subscription or disable API keys.
at kmf (workbench.desktop.main.js:9095:38083)
at Cmf (workbench.desktop.main.js:9095:37240)
at $mf (workbench.desktop.main.js:9096:4395)
at ova.run (workbench.desktop.main.js:9096:8170)
at async qyt.runAgentLoop (workbench.desktop.main.js:34193:57047)
at async Wpc.streamFromAgentBackend (workbench.desktop.main.js:34242:7695)
at async Wpc.getAgentStreamResponse (workbench.desktop.main.js:34242:8436)
at async FTe.submitChatMaybeAbortCurrent (workbench.desktop.main.js:9170:14575)
at async Object.$i [as onSubmit] (workbench.desktop.main.js:32991:3808)
at async workbench.desktop.main.js:32965:60145
Caused by: ConnectError: [resource_exhausted] Error
at uKd.$endAiConnectTransportReportError (workbench.desktop.main.js:11431:32845)
at w0t._doInvokeHandler (workbench.desktop.main.js:33981:23171)
at w0t._invokeHandler (workbench.desktop.main.js:33981:22913)
at w0t._receiveRequest (workbench.desktop.main.js:33981:21545)
at w0t._receiveOneMessage (workbench.desktop.main.js:33981:20362)
at lin.value (workbench.desktop.main.js:33981:18389)
at Oe._deliver (workbench.desktop.main.js:49:2962)
at Oe.fire (workbench.desktop.main.js:49:3283)
at R3t.fire (workbench.desktop.main.js:11415:12156)
at MessagePort. (workbench.desktop.main.js:36042:18408)

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report. This isn’t a bug. Using your own API keys (BYOK) in Ask mode now requires a Pro subscription on all plans.

It used to work on the Free plan as an undocumented option, but that behavior has changed. The team is aware of this change.

Options:

  • Upgrade to Pro to keep using BYOK in Ask mode
  • Use Cursor’s free models (without your own API keys) on the Free plan

I get that it’s annoying when something used to work and then stops.