Switched to Composer 2 after reaching API limit on every request

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor keeps showing:

“Switched to Composer 2 after reaching API limit”

on every request even though usage is not exhausted.

The issue appears after every message, including simple prompts like “hello”.

Steps to Reproduce

  1. Open Cursor
  2. Use Ask mode
  3. Select GPT-5.5
  4. Send any message
  5. Toast appears:
    “Switched to Composer 2 after reaching API limit”

Expected Behavior

Cursor should use the selected model normally without triggering Composer fallback or API limit warnings.

Screenshots / Screen Recordings

Ekran görüntüsü 2026-05-18 163343.png
Ekran görüntüsü 2026-05-18 163343.png439×781 14.4 KB

Operating System

Windows 10/11

Version Information

Version: 3.4.20 (system setup)
VSCode Version: 1.105.1
Commit: 0cf8b06883f54e26bb4f0fb8647c9500ccb43310
Date: 2026-05-15T02:26:10.351Z
Layout: editor
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: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

GPT-5.5, Sonnet 4.6

For AI issues: add Request ID with privacy disabled

f9a7046a-279b-47e5-ab48-6e8dc12daba1

Additional Information

Additional troubleshooting already attempted:

  • Fully reinstalled Cursor
  • Cleared all local cache/state
  • Removed all Cursor folders from AppData
  • Disabled Agent mode
  • Disabled Auto routing
  • No personal API keys connected
  • GPT-5.5 still responds normally, but the fallback toast appears every message

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

Hey, this isn’t a bug, it’s expected behavior, but I agree the toast wording is confusing and it’s already on our radar.

What’s happening: you’ve used up your premium model limit in the Pro plan, which includes GPT-5.5 and Sonnet 4.6. When you pick GPT-5.5 and send a message, the system auto-routes the request to Composer 2 because your premium quota is exhausted. That’s why the toast shows every time. Nothing is broken, the premium allocation will stay exhausted until your cycle resets.

From usage data: you went over the premium limit on May 13, and since May 14 all your requests, about 80 to 420 per day, have been running on composer-2-fast. GPT-5.5 hasn’t actually been used in the last week, the toast only appears when you try to select it.

Options:

  • Wait for your usage cycle to reset, you can see it in Dashboard > Manage Subscription
  • Manually select Auto or Composer 2 and the toast will go away
  • Enable usage-based pricing in billing settings if you need premium models beyond the included quota

Reinstalling, clearing cache, and Request ID won’t help here. This is server-side quota logic, not a client bug. I’ve shared feedback with the team about the unclear modal copy, no ETA yet for a wording update.