Cursor Composer 2.5 may use fast mode even when it is disabled
In one experience, Cursor's suddenly began completing work much faster after about two months of normal default-mode use. was intentionally avoided because its speed was not worth a reported sixfold usage charge on a limited budget. Turning off made no difference, and manually enabling it produced the same apparent speed.
was also disabled for , and a rule was added telling Cursor never to use it, but the behavior continued. It remains unclear whether usage was actually deducted at the fast-mode rate.
Key points
- appeared to run at fast-mode speed while was disabled.
- reportedly carries a sixfold usage charge.
- Disabling for did not change the behavior.
- A rule forbidding also had no effect.
- The report does not confirm whether usage was deducted at the higher rate.