I’m still on a yearly Pro plan and have made decent progress with a grok / opus mix with the exception of regular disconnect loops and remote freezing. However, after burning up the extra models API in 2 days and an extra $25 on demand in just 1 hour it seemed sensible to try claude code. Opus always produces better work and is useful for calling out mistakes made by grok. I’ve now signed up to a CC $20 pro plan CLI and so far have completed 2 full days of work and still within the weekly limit - a far better tradeoff than paying extra for on demand usage. CC CLI has many advantages as it’s engineered to optimize token usage and stores your code in memory whereas cursor typically dumps huge multi-million tokens in one turn thus maxing out in minutes. Cursor desperately requires efficiency improvements. It’s still decent and useful but I’ll avoid renewing unless this changes.
DanSt
(Daniel)
15
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Stick with Cursor or switch to Claude Code? 🤔 | 14 | 8011 | April 9, 2026 | |
| [poll] What's your current opinion on Cursor's pricing? | 5 | 552 | January 3, 2026 | |
| Cursor vs Claude Code — Experiences with Cost and Performance | 2 | 1083 | March 9, 2026 | |
| Long time cursor user now switching | 8 | 924 | February 10, 2026 | |
| $200 Claude/cursor vs $200 Claude CLI | 14 | 9271 | July 12, 2025 |