BYOK Got Blocked in 0 limit left

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

So I already saw another topic that there’s a bug when the I got limit then the BYOK request got blocked by client validation in latest version

So my question is just simple would it worked when I downgrade to lower version like Cursor version 2?

Steps to Reproduce

Cursor pro got 0 limit left then use BYOK

Operating System

MacOS

Version Information

Version: 3.4.17
VSCode Version: 1.105.1
Commit: 93e603f703cd553a6bb3644711a3379bbbb31180
Date: 2026-05-13T21:39:55.724Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.4.0

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, this isn’t a bug and it isn’t client-side validation. BYOK for Agent and Edit requires a paid subscription Pro or Teams. On the Free plan, these features are blocked server-side when you use your own API key, so rolling back to Cursor v2 won’t change anything. The restriction applies in any version.

From what we can see, the email on the forum account is currently on the Free plan with no active subscription. You might have seen reports about a similar but different bug where Pro users were incorrectly blocked by a client banner, and that’s already been fixed. That doesn’t apply to the Free plan.

If you want to use your own key for Agent or Edit, you’ll need Pro: Pricing and plans | Cursor Docs

hi @deanrie
i’m replying from my enterprise email account

and this is the evidence

are you sure it’s fixed?

From the screenshot, I can see the standard team usage limit message, but I don’t see clear signs that a BYOK request is what’s getting blocked. To figure it out, I need a few details:

  1. Is BYOK actually set up on the team account (your own API key added in Cursor Settings, and BYOK enabled in the team admin settings)? Or did you just hit the team usage limit without BYOK?
  2. If BYOK is set up and the request fails with it, please send the Request ID for that request (Chat > three dots in the top right > Copy Request ID).
  3. A screenshot of the exact error or popup when you send the request would also help.

If BYOK isn’t set up on the team, then “team usage limit reached” just means the team limit is used up, and the team admin needs to raise the limit (the Request Limit Increase button on the screenshot goes to them).