In this categoryCursor · 26
- How to Install Cursor and Import VS Code Settings (6 Minutes)Start
- Cursor Setup Guide: From Install to Your First AI Edit
- How to Set Up Project Rules in the .cursor/rules Folder
- How to Set Up Codebase Indexing in Cursor
- How to Enforce Project Conventions with Cursor Rules
- How to Write a Team Rule That Applies Only to Certain Files
- How to Migrate a Legacy .cursorrules File to the New Rules Folder
- How to Use Cursor Rules to Guide AI Edits
- How to Set Project Rules in Cursor
- How to Add a .cursorrules File to Steer Cursor
- How to Customize Cursor Keyboard Shortcuts
- How to Edit Multiple Files at Once with Cursor Composer
- How to Use Cursor Tab Completion Effectively
- How to Edit Code Inline with Cmd+K in Cursor
- How to Add Context to Cursor Chat with @ Mentions
- How to Choose and Switch AI Models in Cursor
- How to Add Library Docs as Context with @Docs in Cursor
- How to Generate and Maintain Tests with Cursor Composer
- How to Undo a Composer Change with Checkpoints in Cursor
- How to Use Cursor Agent Mode to Build a Feature End to End
- How to Connect an MCP Server to Cursor
- How to Refactor Across Your Whole Codebase in Cursor
- How to Query Your Database from Cursor with a Postgres MCP Server
- How to Let Cursor Run Commands Automatically (and Keep It Safe)
- How to Build a Full Feature Across Frontend and Backend with Composer
- How to Debug an MCP Server That Will Not Connect in Cursor
How to Choose and Switch AI Models in Cursor
Pick the right model per task, switch it from the chat box, and understand what Auto mode does for you.
Cursor lets you pick which AI model handles a request, and the choice matters: some models are faster and cheaper, others reason harder on tricky problems. This guide shows where to switch models, how Auto mode decides for you, and a simple way to match the model to the task.
What you need
- Cursor installed and signed in
- An active plan or trial that includes model access
- A task in mind, from a quick edit to a hard refactor
Step 1: Open the model picker
Open the chat pane and look at the bottom of the input box. The model name sits next to the send button. Click it to open the picker, which lists the models available on your plan plus an Auto option.
Step 2: Understand Auto mode
Auto lets Cursor pick a model for each request based on the task and current capacity. It is a good default for everyday work because it balances speed and quality without you thinking about it. When you need predictable behavior, pin a specific model instead.
Step 3: Match the model to the task
Use a fast model for small, well-defined edits where you already know the answer. Reach for a stronger reasoning model when the change spans many files, involves tricky logic, or you are stuck and need it to think.
| Task | Pick |
|---|---|
| Rename, small tweak, boilerplate | Fast / lightweight model |
| Everyday feature work | Auto |
| Multi-file refactor or hard bug | Frontier reasoning model |
| Long planning before coding | Frontier reasoning model |
Step 4: Switch mid-conversation
You can change the model between messages in the same chat. If a fast model gets stuck, switch to a stronger one and ask it to continue; it keeps the conversation context, so you do not start over.
Result: you spend reasoning capacity where it pays off and keep simple edits cheap and instant, instead of running everything through the most expensive model.
Watch related tutorials
33:42
41:18
28:05
3:12
26:54
39:10New guides in your inbox
Fresh step-by-step how-to guides as we publish them. One email a week, no more.