Cursor forces usage of composer-2-fast and its expensive and can't be disabled
By EpicPulse839 · ISSUE · About Cursor
I am on the old requests-based plan of 500 requests. I use opus and for each message/request cursor charges me not only for the opus, but also for (sometimes) two times two composer-2-fast requests for \*something\*.
Effectively what was 1 request now becomes 5 requests... This means that instead of having ±25 requests per workday I now have just 5, which is not really enough. If I dont find solution soon, Im switching to claude code. Also I have composer-2-fast disabled in models, checked all the settings but couldn't find anything else to help.
Does anyone have a solution?
27 upvotes · 7 comments
Comments (7)
AlexChen: Solution is to revert your cursor to 4.2, there’s a github repo that gives all the previous versions. I have v4.2 and it works like before, with no subagents.
SwiftMaker952: This sucks, no matter the model I choose for a Plan, it spawns 2-3 Composer 2 models to get information from the codebase (it appears) and then use the model I chose, to write the plan; this sounds great in theory, but it sucks in practice because Composer 2 normally misses important bits of informa
DigitalHawk9933: This is only on request based plans and is documented in their documentation. Once on a non request based plan they will use the model you choose.
Update: This is not actually in documentation but listed on forums
[https://forum.cursor.com/t/subagent-model-selection-not-respected/155506](https://
SarahKim: "Don't use subagent for this session" at the end of every prompt
Works everytime. For me at least
Well, subagent has benefits but sometimes it will spawn on unnecessary situation and for request-based legacy pricing users, it is bad news since it will cost 2 credits no matter how small or large the
SarahKim: This was also getting on my nerves recently, using "Don't use a subagent for this session" fixed it for me too 👍 Thanks for the suggestion
SwiftMaker952: this is the kind of thing that should be in the changelog, not something you discover by watching your request count drain 5x faster than expected.
if you do switch to Claude Code - the per-token pricing is actually more predictable once you get used to it. no hidden multipliers from internal routi
ShadowVibe354: I’ve found composer 2 to be bad.
More discussions about Cursor on HonestUse