Pro BYOK blocked: MiniMax-M2.7 auto-switches to default even with on-demand enabled (v3.11.13)

Support Bug Reports
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

I am on Cursor Pro. My included Cursor usage pools are exhausted, but I have plenty of quota on my own MiniMax-M2.7 API (BYOK via Override OpenAI Base URL).
MiniMax-M2.7 is configured and enabled in Cursor Settings → Models (Add Custom Model + OpenAI API Key verified).
When Cursor usage limit is hit (and even after enabling On-Demand Usage / pay-as-you-go):

  1. Selecting MiniMax-M2.7 in the model picker immediately jumps back to default (Auto)
  2. The model picker often shows only Auto / Get More Usage
  3. Ctrl + / also shows Get More Usage instead of the custom model list
  4. BYOK requests are blocked despite external API quota remaining
    Local client logs show repeated entries:
    UsageLimitPolicyBanner: BYOK exemption skipped auto-switch currentModelName: MiniMax-M2.7 targetModel: default

Latest reproduction timestamps: 2026-07-12 13:38:59, 13:52:26, 13:53:23
Expected: Custom BYOK model (MiniMax-M2.7) with valid API key should route to the user’s endpoint and bypass Cursor included usage limits.
Actual: Client skips BYOK exemption and force-switches to default. On-demand spending does NOT fix this.
Related: Hard Block on BYOK Usage Despite Pro Subscription ($16/mo) – Version 3.0.16

Steps to Reproduce

  1. Pro subscription, usage pools exhausted
  2. Enable On-Demand Usage on dashboard (optional — bug still reproduces)
  3. Settings → Models → Override OpenAI Base URL https://api.minimax.io/v1 + API Key + Add Custom Model MiniMax-M2.7
  4. Enable only MiniMax-M2.7
  5. Select MiniMax-M2.7 in Agent chat → observe immediate switch back to Auto/default

Request ID

756fc317-088a-4c7b-bff1-253f9ba4cfa0

Operating System

Windows 10/11 (Windows_NT x64 10.0.26200)

Operating System

Windows 10/11

Version Information

  • Cursor Version: 3.11.13 (user setup)
  • VSCode Version: 1.105.1
  • Layout: unifiedAgent
  • Build Type: Stable

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report. I’ll break down what’s going on.

What you’re seeing is expected behavior, not a bug. BYOK models (a custom model via Override OpenAI Base URL) in Agent/Chat/Edit require an active paid subscription (Pro or higher). This is also confirmed in MiniMax’s official docs for Cursor: “Custom models require a Cursor Pro subscription or above” Cursor - MiniMax API Docs.

When included usage runs out and there’s no active paid subscription, the client won’t let you switch to a custom model. That’s why it snaps back to Auto/default and the model picker shows Auto / Get More Usage. Turning on On-Demand Usage doesn’t help here, because it also requires an active paid subscription. The line in your logs (BYOK exemption skipped auto-switch ... targetModel: default) is the expected logic working correctly. The old 3.0.x bug that forced auto-switching was fixed in 3.11.13, so this isn’t that bug coming back.

Please check your subscription status in the dashboard at cursor.com > Manage Subscription. Based on what the picker shows, your account likely isn’t on an active paid plan right now. Once it’s active, MiniMax-M2.7 should be available in Agent again.

If you’re sure your subscription should be active and something doesn’t match, email [email protected] and they can check your account details.