Cursor Auto-Switches to Composer 2.5 After API Limit Is Reached, Causing Context Window Loss

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hi,

i have context window of 480K+ on fable 5

i reached the limit so now cursor switched to composer 2.5
causing me to lost the context

i want to continue after renew the subscription but now i cant

i cant even see the thinking process of the session, everything disappeared,

not only that: i just noticed that all files created by the last prompt does not appear in the session, although it is on the disk

Steps to Reproduce

use any model that has context window more than composer 2.5 can handle,
and reach your API limit,
cursor will redirect to composer 2.5 causing you context losing

Expected Behavior

cursor should just stop

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.10.11
VS Code Extension API: 1.125.0
Commit: 4ef9fe3d055f8c4523179a090f14eb835bc3c940
Date: 2026-07-03T04:44:14.398Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

Fable 5

For AI issues: add Request ID with privacy disabled

ab450108-f4b4-4e6f-b9cc-46130e0ded6f

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.


Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!


Expected Behavior
What is meant to happen here that isn’t working correctly?


Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)


Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)


For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…


Additional Information
Add any other context about the problem here.


Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

Hi there,
When you hit your API usage limit, Cursor auto-switches you to Composer 2.5 instead of stopping or staying on a model that still has room. We agree it shouldn’t silently downgrade you like that.

The important part: your work isn’t lost. Your files are safe on disk (as you noticed), and the conversation itself isn’t deleted on our side. Because Composer 2.5 has a much smaller context window than Fable 5, the session view collapses and summarizes the earlier turns, which is why the thinking steps and recent edits look like they vanished from the panel even though nothing was removed.

To keep working on Fable 5: enable on-demand usage (or wait for your monthly usage to reset), then reselect Fable 5 from the model picker and continue in the same thread. With on-demand enabled, you stay on your chosen model at the same API rates without being downgraded. Details here: Usage and limits.

There isn’t a setting today that forces a hard stop instead of the switch, but that behavior (stop, or fall back to a model that actually has room) is exactly what we’re looking at.