Whenever I choose composer-2.5 not fast model and send the prompt in the cloud agent, once it starts running, and I click on the prompt, I see that it’s actually running composer-2.5 fast, which consumes way too much from my usage and I don’t want that. I have to manually toggle off the fast option and send it again.
Steps to Reproduce
Send a prompt with composer-2.5.
Once the agent starts running, click on the sent prompt.
Expected Behavior
It’s meant to show composer-2.5 not fast as the model being used.
I checked the cloud agents you started from the desktop app over the last few days. Every one of them ran on the regular Composer 2.5, not the Fast variant, and there are no Fast charges on your account since September 10. So what you are seeing looks like a display issue in the model picker after the agent starts, not the agent actually switching models.
You can double check this yourself on cursor.com/dashboard under Usage: the model column for those requests should say composer-2.5 with no “fast” in it. If you spot any rows there that do say composer-2.5-fast from a cloud agent, send me the time and I will take a closer look.
To help us pin down the display problem, could you send:
A screenshot of exactly where you see “Composer 2.5 Fast” after clicking the prompt (the picker in the message box, or somewhere else).
The link to that agent (right click the agent in the sidebar, or copy the cursor.com/agents/bc-… URL from the web).
In the meantime you do not need to toggle Fast off and resend, the run is already on the regular model!
That chart is cumulative for the billing period, so it only ever goes up or stays flat, and a flat line means no new usage. All of the Composer 2.5 Fast usage in your screenshot happened between August 23 and September 6, and nothing has been added since. Almost all of it came from the desktop app and from agents launched on cursor.com in late August, when Fast was still switched on in the picker. Every cloud agent you have started in the last few days, including the ones from this morning, ran on regular Composer 2.5!
One tip: when you launch an agent from cursor.com/agents, the picker there currently defaults to Fast for Composer 2.5, so toggle it off before you send. Launching from the desktop app is fine as is.
If you still see “Composer 2.5 Fast” in the picker after an agent starts, a screenshot of exactly where it appears plus the agent link (right click it in the sidebar, or copy the cursor.com/agents/bc-… URL) would help us fix the label.
Here’s an example of it happening right now.
bc-7ceaf442-5eef-4a2a-9226-9b20fe628e5ecursor://anysphere.cursor-deeplink/background-agent?bcId=bc-7ceaf442-5eef-4a2a-9226-9b20fe628e5e
Hey @aydela, sorry for the slow follow-up here, and thanks for sending that example.
Quick recap: that agent (and every cloud agent you’ve started since) ran on regular Composer 2.5, not Fast, and you have no Fast charges since early September. The “Composer 2.5 Fast” you saw was only a label problem in the desktop app right after launching an agent.
A fix for that label went out in version 3.22.5, and you are already on a newer build. Could you start one cloud agent with Composer 2.5 (Fast off), click the prompt once it’s running, and let me know whether it now shows plain “Composer 2.5”?
