Basics
Get productive in Cursor fast — the core edit loop and shortcuts.
It's VS Code, with the AI moved inside
If you have used VS Code, Cursor will feel familiar on day one — it imports your extensions, themes, and keybindings. What changes is where the AI lives: instead of copying code out to a separate chat, the assistance happens inside the editor, aware of the file you are in and the project around it. The quickest way to feel the difference is to stop pasting into a chatbot and start editing in place. That shift, more than any single feature, is what Cursor is for.
Learn inline edit first
The move you will use most is inline edit — select some code, describe the change, and let Cursor rewrite it in place with full awareness of the surrounding file. It is faster than round-tripping through a chat window and keeps you in flow. Pair it with tab-completion that understands your current file, and you have the core loop. Everything more advanced in Cursor — rules, indexing, the agent — builds on this foundation, so it is worth getting comfortable here first.
The basics topics to explore
This section covers getting started (install, import your VS Code setup, first AI edit) and inline edit (the Cmd-K loop you will lean on daily). Work through the cards below to build the core habits before moving to the agent.
How do I start using Cursor?
Install Cursor, import your VS Code settings when prompted, and try an inline edit — select some code and describe the change. It feels like the editor you know, so the learning is about the AI features, not the interface.
Is Cursor just VS Code with AI?
It is built on VS Code and imports your extensions and settings, but the AI is integrated into the editor rather than bolted on — aware of your files and project. That in-editor context is the real difference from using a separate chatbot.
What is inline edit in Cursor?
Inline edit lets you select code, describe a change, and have Cursor rewrite it in place with awareness of the surrounding file. It is the fastest, most-used move in Cursor and the foundation for everything more advanced.
Can I use my VS Code extensions in Cursor?
Yes. Cursor imports your extensions, themes, and keybindings, so your existing setup carries over and the editor feels immediately familiar. The getting-started cards below cover the import step.
Do you know the Cursor basics?
Four questions on getting started in Cursor and the Cmd-K inline edit loop you'll use more than anything else. No sign-up, instant score, and you can share how you did.
-
Q1 What's the best way to evaluate Cursor when you first install it?Why
Cursor's whole advantage is codebase awareness, and a scratch file gives it nothing to be aware of — you end up judging the tool on the one task it can't help with. A huge unfamiliar repo is the opposite error: all noise, and you blame the tool.
-
Q2 What does the Cmd-K inline edit loop actually do?Why
Select, describe, review the diff, apply. It's the fastest and most controlled way to use AI in Cursor, precisely because the change stays scoped to what you selected and you see exactly what changed.
-
Q3 You've selected one function and typed an instruction about restructuring the whole file. What's wrong?Why
An inline edit acts on what you selected. Asking it for changes beyond that scope is a mismatch — use the right tool for a multi-file change rather than fighting the selection.
-
Q4 The diff looks right at a glance. What should you do?Why
The reviewable diff is the safety mechanism — skipping the review throws away the main thing that makes inline edit safe. Speed comes from the loop being tight, not from not looking.