
How to Set Up Cursor AI
Install Cursor, configure your AI model, create project rules, and build your first feature. Everything you need to go from download to shipping code.
Prerequisites
- A computer running macOS, Windows, or Linux
- Internet connection (for download and AI features)
- A Cursor account (free tier available, Pro is $20/mo)
- Optional: an existing project you want to work on
Download Cursor
Head to cursor.com and click the download button. Cursor detects your OS automatically — you will get the right installer for Mac, Windows, or Linux.
The download is around 200 MB. While it downloads, this is a good time to think about what you want to build first.
Coming from VS Code?
Install Cursor
Mac: Open the .dmg file and drag Cursor to your Applications folder. Launch it from your dock or Spotlight.
Windows: Run the .exe installer. Follow the prompts — defaults are fine. Cursor adds itself to your PATH automatically.
Linux: Download the .AppImage, make it executable with chmod +x, and run it.
On first launch, Cursor asks if you want to import VS Code settings. If you have VS Code installed, say yes — it brings over your extensions, themes, and keybindings.
Sign In
Cursor requires an account to use AI features. You can sign up with Google, GitHub, or email. The free tier gives you a limited number of AI requests per month — enough to evaluate the tool.
Cursor Pro ($20/mo) removes limits on fast AI requests and gives you access to all models. If you are evaluating Cursor against other tools, the free tier is enough to get a feel for it.
Free trial strategy
Choose Your AI Model
Open Settings (Cmd+, on Mac, Ctrl+, on Windows) and navigate to Models. Cursor supports multiple AI models:
- Claude (Anthropic) — Best for complex reasoning, refactoring, and understanding large codebases. Recommended for most development work.
- GPT-4o (OpenAI) — Fast and capable. Great for quick edits, code generation, and general-purpose tasks.
- Gemini (Google) — Good at processing long context. Useful when you need to reference many files at once.
- Custom / API keys — You can add your own API keys for any supported provider if you want more control over costs.
Create a Project
Open a folder in Cursor — either an existing project or a brand-new empty directory. You can use File > Open Folder or drag a folder onto the Cursor window.
If you are starting fresh, create a new folder first:
mkdir my-first-cursor-project
cd my-first-cursor-projectThen open it in Cursor:
cursor .Cursor indexes your project files in the background. For large projects (10,000+ files), the initial index takes a few seconds. After that, it is instant.
Get the Vibe Coding Cheat Sheet
Best tool for every use case + pricing + pro tips. One page, zero fluff. Plus weekly updates on new tools.
Write Your First Prompt
Press Cmd+L (Mac) or Ctrl+L (Windows) to open the AI chat panel. This is where you talk to the AI about your code.
Try a real prompt. If you opened an empty project, try:
Create a simple Express.js server with a health check
endpoint at /api/health that returns { status: "ok" }.
Include a package.json with the right dependencies.Cursor will generate the files and show you a diff. Review the changes, then click Accept to apply them. You can also edit the generated code before accepting.
If you opened an existing project, try asking a question about your code:
@codebase How is authentication handled in this project?
Which files are involved?Good prompts are specific
Configure .cursorrules
Create a file called .cursorrules in your project root. This file tells Cursor about your coding preferences, tech stack, and project conventions.
Here is a practical example:
# .cursorrules
## Tech Stack
- Framework: Next.js 15 (App Router)
- Styling: Tailwind CSS
- Database: Supabase (Postgres)
- Language: TypeScript (strict mode)
## Conventions
- Use functional components with hooks
- Prefer server components; add 'use client' only when needed
- Use absolute imports from @/ prefix
- Error handling: always wrap async operations in try/catch
- Name files in kebab-case, components in PascalCase
## File Structure
- app/ — routes and layouts
- components/ — reusable UI components
- lib/ — utilities and helpers
- types/ — TypeScript type definitions
## Do Not
- Use any CSS-in-JS libraries
- Create files over 300 lines — split into smaller modules
- Use default exports for non-page componentsBuild Something Real
Now that you have Cursor set up, it is time to build. Press Cmd+I (Mac) or Ctrl+I (Windows) to open Composer — Cursor's multi-file editing agent.
Composer is different from the chat panel. It can create, modify, and delete multiple files in a single operation. Describe a feature and let it work:
Add a user profile page at /profile that:
- Shows the user's name, email, and avatar
- Has an "Edit Profile" button that opens an inline form
- Saves changes to the database via a PATCH /api/users/me endpoint
- Shows a success toast after saving
- Handles loading and error statesComposer will plan the changes, create or modify the necessary files, and show you a complete diff. Review each file, make adjustments if needed, and accept.
Iterate, don't restart
What to Build First
Personal Portfolio Site
A responsive portfolio with a hero section, project cards, and a contact form. Start with "Create a modern portfolio site with Next.js and Tailwind CSS."
REST API with Auth
Build an Express.js API with JWT authentication, CRUD routes, and input validation. Use Composer to scaffold the whole thing at once.
Real-Time Chat App
A WebSocket-powered chat application with rooms, typing indicators, and message persistence. Great for testing multi-file editing.
Cursor Tips from Power Users
Use @-mentions for context
Type @filename, @folder, or @codebase in chat to give Cursor precise context. @codebase indexes your entire repo — use it for questions about architecture.
Tab is your best friend
Cursor Tab predicts your next edit, not just your next line. Start typing and watch it suggest multi-line completions based on your intent. Press Tab to accept.
Composer for multi-file edits
Use Cmd+I (Mac) or Ctrl+I to open Composer. Describe a feature that spans multiple files and Cursor will edit them all in one go. Review the diff before accepting.
Keep .cursorrules under 500 lines
Long rules files dilute the AI's attention. Focus on your tech stack, coding conventions, and file structure. Skip obvious things like "write clean code."
Switch models per task
Use Claude for complex reasoning and refactoring. Use GPT-4o for quick edits and completions. You can switch mid-conversation in the model dropdown.
Undo with Cmd+Z works on AI edits
If Cursor writes something wrong, just undo. AI-generated edits are treated like normal edits — Cmd+Z reverses them one step at a time.
Essential Keyboard Shortcuts
| Action | Mac | Windows |
|---|---|---|
| Open AI Chat | Cmd+L | Ctrl+L |
| Open Composer | Cmd+I | Ctrl+I |
| Accept inline suggestion | Tab | Tab |
| Reject inline suggestion | Esc | Esc |
| Open Command Palette | Cmd+Shift+P | Ctrl+Shift+P |
| Toggle terminal | Cmd+` | Ctrl+` |
| New chat conversation | Cmd+Shift+L | Ctrl+Shift+L |
| Add file to context | Type @filename | Type @filename |
You are set up. Now explore.
Compare Cursor against other tools, or submit what you build to the showcase.