Unable to turn off "Switched to Composer 1.5 after reaching API limit."

[joeylynchhh]

Hello,

I am using Cursor for research purposes. I set fixed limits on API usage to manage and track spending given the expense is quite high. Recently, as in the last 7 days, Cursor has begun automatically switching my preferred to model to Composer 1.5 when the API limit is reached and automatically begins performing the request. This happens every single time an API limit is reached. This leads to the following work-flow:

1. Run task unaware if API is reached

2. if API limits is reached, Cursor automatically runs the request in composer without approval.

3. I need to stop the current task

4. I need to change the model back to whatever I was currently using.

5. I need to update the API usage

6. I need to rerun the task once API usage has been increased.

This work-flow included steps 1, 5, and 6 until I noticed the change on 2/23/2026. That is a 50% increase in work-flow when running requests with no way I can identify to shut it off. It is a useless frustration I should not experience countless times a day. I was perfectly happy when the work-flow included steps 1, 5, and 6 since it let me keep track of the usage.

First, how do I shut off this useless feature? Second, how do I change the setting to prevent Cursor from changing the model I purposely selected for the task?

I spend hundreds of dollars a month on usage. This UX, in combination with cursor forcing us to manually shut off commit attribution no one ever agreed to use, is becoming frustrating to work with.

[Colin]

Hey there.

If you disable Composer 1.5 in Agent settings > Models, the fallback should not switch the model to Composer 1.5.

That said, there’s some variable logic based on plan type and other factors that might affect this. If you get switched again, can you grab the Request ID for that chat?

[joeylynchhh]

Hi Colin, thank you for reaching out. Turning off the composer models unfortunately does not change the experience. I created the experience this morning in Request ID: 8267831a-2616-446e-94d4-53ffcea6ba44 despite composer being turned off. I feel this is a useful feature if we opt-in to it. However, I would like to opt-out (with the ability to change that depending on the circumstance) since it isn’t helping my current work-flow. I attached an image of the notification that appears when replicating the problem.

[simkiiiii]

I am experiencing the same issue. It is urgent that this problem be resolved.