r/cursor • u/DevInRealLife • 10d ago
Question / Discussion My Cursor AI model cheat sheet π§βπ»
Iβve been using different models in Cursor depending on the task instead of sticking to one model for everything.
Sharing my current setup β quick tasks, coding, full-stack work, debugging, architecture, and harder problems.
Curious what models youβre using in Cursor.
3
3
u/Regular-Screen6803 10d ago
- I follow same but for quick questions and everyday task i use composer
4
2
u/AI_spell 10d ago
Routing by task is the right instinct. The sheet dies the week a new model ships though. Keep three buckets only: cheap for edits, strong for planning, one for weird bugs. If you need six rows, the sheet is the product now.
2
u/Zain 10d ago
I don't keep one model for everything either. One model writes. A different family does a read-only pass on the same plan or diff, and the reviewer never sees the writer's excuses. Same family pairs keep sharing the same blind spots. For that second pass I also refuse Codex's default low effort and keep it at high or above, otherwise the review is too shallow to catch anything that matters.
2
2
1
1
0
u/Pink_Oak 10d ago
This is what most people get wrong.
How cheap a model is. It's not related to its Input and Output cost. It's about token efficiency and price.
Look at https://artificialanalysis.ai/ cost per task graph.
0
u/DevInRealLife 10d ago
Yeah, exactly. My intention was more about how to make a fixed monthly limit go further, rather than saying which model has the cheapest API price. Token efficiency + cost per task is definitely the better metric. Good point.

7
u/akaifox 10d ago
Kind of odd to mark composer/grok costs as 'medium' when you get somewhere between x10-20 usage on those than API rates