How to Use Cursor for Beginners: Your First Hour

How to use Cursor for beginners, without freaking out

Cursor is a code editor with an AI assistant built in. You type what you want in plain English, it writes the code, and you decide whether to keep it. That’s the whole idea. If you’ve never written a line of code, this guide on how to use Cursor for beginners walks you through the first hour: install it, open a project, generate something, run it, and fix it when it breaks.

A quick word before we start. Cursor looks more “technical” than a browser builder, because it shows you actual files. That’s a feature, not a problem. Seeing the files is how you slowly learn what software is made of. You don’t need to read or understand the code yet. You just need to learn the loop: ask, look, run, fix, repeat.

What Cursor actually is (in plain English)

A “code editor” is just a fancy text program where software gets written. Cursor is one of those, with a chat panel bolted on. When you ask the chat to do something, it edits the text files in your project for you. Think of it like a very capable assistant sitting next to you: you say “add a contact form,” it does the typing, and you sign off on the result.

Two terms you’ll see a lot:

• A project (or folder): all the files for one thing you’re building, kept together in one folder on your computer.
• The terminal: a black text box where you type commands to run your app. Cursor has one built in. You’ll use it a little, and that’s fine.

If you want the bigger picture of what this style of building is, the plain-English intro to vibe coding sets the stage. This article stays focused on Cursor specifically.

Step 1: Install Cursor and open it

Go to the Cursor website, download the version for your computer (Mac or Windows), and install it like any other app. When you first open it, it’ll ask a few setup questions and may offer to import settings. You can accept the defaults. There’s nothing here you can break.

When it finishes, you’ll see a mostly empty window with a sidebar on the left and a chat panel (usually on the right). That chat panel is where you’ll spend most of your first hour.

Step 2: Open a project folder

Cursor needs a folder to work in. Two easy ways to start:

1. Create an empty folder on your desktop, name it something like my-first-app, then in Cursor choose “Open Folder” and pick it.
2. Let the AI scaffold one for you by describing what you want once the folder is open.

For your very first try, keep the goal tiny. A single web page that says hello and has one button is perfect. The point of hour one is not to build your dream product. It’s to feel the loop work.

Step 3: Generate something with chat

Open the chat panel and describe what you want in normal words. Be specific about the outcome, not the technology. For example:

Create a simple web page with a heading that says
"Hello from my first app" and a button that shows
a small message when clicked. Keep it to one HTML file.

Cursor will think for a moment and then propose changes. You’ll see it suggest creating a file (something like index.html) and fill it with code. You do not need to understand that code. Your job is the next step: deciding whether to keep it.

If you’re not sure how to phrase requests, our guide on writing prompts that build apps goes deeper. The short version: say what you want, where it should go, and one constraint (like “keep it simple”).

Chat vs. inline editing

You’ll notice Cursor offers a few ways to ask for changes. The chat panel is the friendliest for beginners, because it explains what it’s doing and shows changes you approve. There’s also a quick inline edit (often opened with a keyboard shortcut) for tweaking a specific spot. Start with chat. You can explore the rest once the loop feels natural.

Step 4: Accept or reject the changes

This is the most important habit in the whole tutorial, so slow down here.

When Cursor proposes an edit, it shows you a “diff” — a before-and-after view. New or changed lines are usually highlighted in green, and removed lines in red. You’ll see two buttons, roughly “Accept” and “Reject” (sometimes “Apply” and “Discard”).

• Accept when the change looks like it matches what you asked for.
• Reject when something seems off, or when you simply want to ask for it differently.

You are allowed to reject freely. Rejecting doesn’t break anything. It just means “not this, let me ask again.” Early on, you’ll accept most things because you can’t yet judge the code. That’s normal. As you do more reps, you start noticing when an answer doesn’t smell right — and that instinct is the real skill.

A safety tip: turn on version history early. If you initialize “git” (Cursor can do this for you if you ask in chat), you get an undo button for your whole project. Then no mistake is permanent.

Step 5: Run it and see it work

Generating code is only half the loop. You have to run it to see if it actually works.

For a single web page, the simplest path: ask Cursor in chat, “How do I open this page in my browser?” It’ll either give you a one-line command for the built-in terminal, or tell you to double-click the file. For anything bigger, you’ll usually run a command like the one Cursor suggests, then open a local address (often something like http://localhost:3000) in your browser.

When it runs, look at the result with fresh eyes. Does the button do what you asked? Does the heading say the right thing? If yes, you just completed your first full loop. If no, on to the best part.

Step 6: Ask Cursor to fix its own errors

Things will break. A button won’t click, the page will look wrong, or you’ll get a scary red error message. This is completely expected, and Cursor is good at fixing its own work — if you tell it what’s wrong.

The move is simple: copy the error message (or describe what you see) and paste it into chat.

When I click the button, nothing happens.
Here's the error I see in the browser console:
[paste the red error text here]
Please fix it.

A few beginner tips for this part:

• Show, don’t summarize. Paste the exact error text. “It’s broken” gives Cursor nothing to work with.
• One problem at a time. Fix the button before you ask for three new features.
• If the fix makes it worse, reject and try again. Reword your request rather than piling fixes on top of fixes.

If you hit a blank page or a confusing crash, two focused guides help: the calm debugging loop for AI code, and the specific case of the white-screen error.

Setting expectations for hour one

Let’s be honest about what your first hour is and isn’t.

• It is: learning the rhythm of ask, look, accept, run, fix. That rhythm is the foundation for everything else.
• It isn’t: building a finished, polished product. Don’t judge yourself by the output yet.

You will feel slow. You’ll accept code you don’t understand. You’ll get errors that look intimidating. All of that is the normal beginner experience, not a sign you’re bad at this. The people who get good simply did the loop more times than the people who quit.

Key takeaways

• Cursor is an editor where you describe what you want and the AI does the typing.
• The core loop is: ask in chat, review the diff, accept or reject, run it, paste errors back to fix.
• Keep your first project tiny and turn on version history so nothing is permanent.
• Understanding the code comes later. Running the loop comes first.

Where to go next

Once the loop clicks, the question becomes how to get fluent fast. The honest answer is reps: short, frequent practice beats one long tutorial you watch passively. That’s exactly what VibeGym is built for — a “Duolingo, but for building apps” approach with bite-sized daily drills across Foundations, Prompting, Debugging, and Security. The skills you practice transfer across Cursor, Claude, Lovable, and Bolt, so you’re never locked into one tool.

A tutorial shows you someone else building. To actually get good, you have to be the one driving — accepting, rejecting, running, and fixing, over and over, until it feels easy.