Cursor Settings That Actually Matter
The Cursor settings that actually matter — model selection, API keys, dot file protection, and the options that change how the AI behaves in your codebase.
Most settings in Cursor are fine as defaults. A few are worth knowing about from day one.
Opening Settings
Cmd/Ctrl + , → VS Code-style settings panel (editor preferences)
Cmd/Ctrl + Shift + J → Cursor-specific AI settingsOr: Gear icon in the bottom left → Cursor Settings.
Model Selection
This is the most important setting for your workflow. Cursor lets you choose which AI model handles interactions.
Where to change it: Cursor Settings → Models
| Model | Best For |
|---|---|
| Claude Sonnet | Daily driver — best balance of quality and speed |
| Claude Opus | Complex, thorny problems — costs more, worth it sometimes |
| Claude Haiku | Fast completions, simple repetitive tasks |
| GPT-4o | Solid alternative, slightly different "feel" |
| Gemini Flash | Speed, great for tab completion |
The practical choice: keep Sonnet as your default. Switch to Opus when you're stuck on something architectural. Use the model picker in the chat panel to switch mid-conversation.
The Key Insight on Model Selection
A small model with a well-detailed plan outperforms a large model with a vague request. Don't default to Opus because you think it'll solve your problems — a clearer prompt to Sonnet will outperform a vague prompt to Opus almost every time.
Save the big models for genuinely hard problems:
- "I've tried three approaches and Sonnet can't figure out why this breaks"
- "I need help thinking through a complex architectural tradeoff"
- "There's a subtle bug and I can't track it down"
API Keys (Bring Your Own)
By default, Cursor's AI usage goes through Cursor's billing. If you have your own API keys for Anthropic, OpenAI, or Google, you can use those instead.
Where to add them: Cursor Settings → Models → scroll down to see API key fields
Why bother:
- Use models not in Cursor's standard menu
- Can be cheaper at high usage volumes if you have enterprise pricing
- Useful if your company has existing API contracts
The catch: rate limits still apply. Anthropic has strict rate limits even on paid plans, especially for Claude Opus. If you're hitting limits frequently, this won't fix it — you need a higher-tier API plan.
Privacy Mode
Where: Cursor Settings → Privacy
By default, Cursor can use your code to improve the model. In Privacy Mode, your code is not sent for training.
Turn this on if:
- You're working with proprietary code
- You're under an NDA
- Your company has data handling requirements
When in doubt, turn it on. There's no downside to Privacy Mode except losing the marginal improvement from contributing training data.
Dot File Protection
Cursor has a setting that determines whether the AI can read and edit your .env files, .gitconfig, and other dot files.
Where: Cursor Settings → Features (look for "Protect Dot Files" or similar)
The default: protected — won't touch them.
Leave this on. An AI agent should never read your .env file. If you need the AI to understand your environment variables, describe them manually:
"The API expects an Authorization header with a Bearer token.
The token is stored in process.env.API_TOKEN. Don't read my .env file —
I'm just telling you the shape of the configuration."This gives the AI what it needs without exposing the actual secrets.
Codebase Indexing
Cursor indexes your codebase to make @codebase references work — searching across all your files when you ask about something.
Worth knowing: when Cursor indexes files, it reads the first 250 lines (100 lines when searching). If your files are 1,000 lines, the AI is guessing about the bottom 750.
This is a practical argument for smaller files. It's also a reason not to put critical logic at the bottom of a large file.
Turn indexing off for:
- Repositories with sensitive data
- Huge repos where indexing is slow and
@codebaseisn't reliable anyway - Private credential stores
VS Code Settings That Still Apply
Cursor is built on VS Code. All VS Code settings apply — workspace settings, language-specific settings, font, theme, keybindings.
If you're coming from VS Code, your existing settings work. You can even import your VS Code profile.
The one setting to check: make sure your workspace TypeScript version matches your project's TypeScript version (bottom right corner of the editor when a .ts file is open). Mismatches cause false positive type errors that confuse the AI.
The Two Settings to Change Immediately
- Privacy Mode → on, if your code is proprietary
- Model → Claude Sonnet as default, switch to Opus for heavy lifting
Everything else can stay at defaults until you have a specific reason to change it.
Keep reading
Enjoyed this? Get more like it.
Deep dives on system design, React, web development, and personal finance — straight to your inbox. Free, always.