@TjG thanks for the report. On the mobile web UI (narrow screen or PWA), the model picker currently only shows the Fast option and you can’t switch it there. This is a known issue we’re tracking, no ETA yet.
A working workaround, it also works for agents started from your phone. Set the Default Model in Cloud Agent settings on desktop or in the full site version. cursor.com/dashboard/cloud-agents → Default Model → hover the model → Edit → uncheck Fast → save. This default is applied server-side when the agent starts, so new agents will start in non-Fast even if the mobile picker still shows the Fast label.
If you see Fast usage charges on the Usage page for an agent that should’ve run in non-Fast, send the agent ID bc-... and we’ll check that specific run.
Where is the Fast usage default on mobile being tracked? I also got burned by this and would like to watch the issue and know when the mobile app is usable again with regard to avoiding fast. Thank you!
Hey, thanks for reaching out. The mobile case is separate from the web part of this thread. On mobile, the web/PWA picker currently only shows the Fast option, and you can’t switch it there. This is a known issue we’re tracking, and we don’t have an ETA yet.
Workaround so agents start in non-Fast even from your phone: set the Default Model server-side. On desktop or the full site, go to cursor.com/dashboard/cloud-agents → Default Model → hover the model → Edit → uncheck Fast → save. This default is applied on the server when an agent starts, so new agents will launch in non-Fast even if the mobile picker still shows the Fast label.
If after setting the server-side default you still see Fast charges on the Usage page for an agent that should’ve been non-Fast, send the agent ID bc-... and we’ll check that run.
Workaround does not work at all. Even if the non-fast model is set as default, cloud agents started in the phone (Android PWA) still use fast. Unnecessary waste of usage.
Is it really that difficult to just add the non-fast option in the mobile picker? Unbelieveable
Hey, thanks for coming back with this. There’s one nuance worth checking on your specific run.
The server-side Default Model is applied when the agent starts, but if the phone picker sends an explicit model choice, it can override that default. On mobile, the picker currently only shows the Fast option, and that’s what we’re tracking right now (no ETA yet).
To understand what actually happened on your side, whether the agent really ran in Fast mode or the picker just showed the Fast label while the run was actually non-Fast, please share the ID of one of those agents (bc-…) that you started from your phone while a non-Fast default was set. I’ll check on our side which model actually executed and how it was billed.
If the Usage page for that agent shows Fast charges, let me know too, and I’ll take a separate look at that run.