Skip to lesson
Exit
Cursor Product & Developer-Workflow Fluency1 / 2

1 min lesson

Model selection - the question platform teams ask first

Explain the practical point behind "The reciting-features version of this question is everywhere."

Step 1 of 2

A platform team will ask which model their engineers should use on day one, and "it depends" is the answer that loses the room. The reciting-features version of this question is everywhere; the depth that distinguishes a real operator is knowing the taxonomy, the cost loop and what Auto is actually doing under the hood.

There are three model categories, and the cue an engineer can see in the picker is the brain icon. A standard model (no brain icon) thinks once and responds - fastest and cheapest. A thinking/reasoning model (brain icon) runs chain-of-thought - slower and consuming far more tokens, so reserve it for deep reasoning, planning or when a standard model has hit a wall. Max Mode greatly enlarges the context window for jobs like auditing a very large codebase - but a bigger context degrades accuracy and costs more, so it's a selective tool, not a default.

Learn more

Advanced table

A complementary split

Category
Standard
Cue / examples
No brain icon; thinks once and responds
When it's the right call
Fast, cheap, everyday completions and small changes
Category
Thinking / reasoning
Cue / examples
Brain icon; chain-of-thought, far more tokens
When it's the right call
Planning, large refactors, when a standard model is stuck
Category
Max Mode
Cue / examples
Greatly enlarged context window
When it's the right call
Auditing a very large codebase - selectively; bigger context trades off accuracy and cost

A complementary split: frontier/high-reasoning models (GPT-5.5, Codex 5.3, Claude Opus 5, Gemini 3.1 Pro) for large refactors and detailed planning vs daily-driver models (Composer, Sonnet 4.6) for easy implementation and small changes. Learn the split, not the roster - the named models turn over every few months.