2 min lesson
Pick the model on three axes, then split plan from execute
Name the three axes you'd score a model on and how that maps to plan-versus-execute work.
Step 1 of 3
Pick the model on three axes, then split plan from execute
A PM-friendly way to reason about model choice is to score every model on three axes: performance, cost and speed. Different tasks want a different mix. For planning and thinking, reach for the most frontier model you have - a GPT-5.x, the current Claude Opus (today Opus 5, which replaced Opus 4.8), or Cursor's own ComposerCursor's own fast coding model, tuned for the editor and priced well below frontier models; the recommended day-to-day model for executing a plan. Press Enter for the full definition., which is frontier-grade and fast. For execution, speed becomes the lever, because a detailed enough plan is something most frontier models can carry out correctly.
Interactive widget. Tab through its controls; the result updates in the panel below as you change them.
Score on performance, cost and speed - then let the task pick the model.