How to Use Claude Code: Step-by-Step for Beginners
How to use Claude Code when you've never written a line of code: from sign-up and install to your first finished task in one evening. Six steps, a live dialogue with the AI, a cheat sheet of buttons and commands, ready-made task phrasing, and fixes for the usual snags. Built for everyone who sells services, courses, and consulting and wants AI to actually do the work, not just give advice.
How to use Claude Code: subscribe to Claude Pro at claude.ai, download the Claude app from claude.com/download, sign in, and open the Code tab. Start a new session, pick an empty folder for the task, and switch to Auto mode. Then describe the task in plain words, for example "build a one-page site for a therapist with a booking button that opens my Telegram." Claude Code writes a plan, creates the files, and shows you the result, and it stops if anything looks unsafe. You check the result and ask for changes.
What's inside
- What you need before you start
- Where to work: the Code tab in the Claude app
- Step 1. Account and plan
- Step 2. Install Claude Code
- Step 3. Working folder and a new session
- Step 4. First task: a live dialogue
- Step 5. Auto mode and the other modes
- Step 6. Project memory: the CLAUDE.md file
- Cheat sheet: Code tab buttons and commands
- How to give tasks: a formula and 12 ready phrases
- Five first projects by profession
- When something goes wrong
- Usage limits and how to stretch them
- Safety: five simple rules
- The whole path in one minute
In my last post I explained what Claude Code is, in plain words. Today is the hands-on part. I've watched the same scene play out many times: someone hears that AI can build websites and bots on its own, gets excited, sees the word Code in the name, and puts it off, because it sounds like a job for a programmer. In reality you install a regular program with windows and buttons and type your tasks in plain words.
The good news: all the difficulty lives in the first twenty minutes. After that it's a regular back-and-forth, like working with a freelancer, except this one never sleeps, never gets sick, and never disappears for a week. So I've laid out the path so you can walk it step by step with a cup of tea and finish the evening holding your first real result.
Section 01What you need before you start
Gather everything up front so you don't have to hunt for anything midway. The list is short.
- A computer. Mac or Windows. A phone won't do for this kind of work: your working folder and its files live on the computer.
- A Claude account with a paid plan. Claude Code comes with Pro ($20 a month, or $17 a month billed yearly), Max ($100 a month), and Ultra ($200 a month). On the free plan, the Code tab asks you to upgrade.
- An email address and a card. Any email works for the account, and a regular credit or debit card covers the subscription.
- Half an hour of quiet time and one small task. There's a whole section on picking the task below, but start thinking now about what's been bugging you: a personal site nobody has time to build, a folder of photos, a sales export you never get around to totaling.
You don't need to know how to program. You don't need technical vocabulary either: Claude Code understands everyday language and answers the same way. If you're still unsure whether to start with Claude at all, I wrote an honest comparison: Claude vs ChatGPT.
Section 02Where to work: the Code tab in the Claude app
The program you install is simply called Claude, and Code is a tab inside it. It's a regular app for Mac and Windows with windows and buttons, and you pick your folder with the mouse. That's all a beginner needs, so you won't burn the evening comparing tools.
I recommend working only here, for two reasons. Claude accounts sometimes get blocked, and when that happens every chat goes with the account, while the files in your working folder stay on your computer. And the regular chat can't publish sites, set up bots, or run agents on its own, while the Code tab can.
| Where | What it is | What you use it for |
|---|---|---|
| The Claude app, Code tab | A regular program. Claude works in a folder on your computer | All the actual work |
| The claude.ai website | Your account and plan settings | Signing up and paying |
| Claude Code in the browser | Runs in the cloud on a GitHub repository, with none of the files from your computer | Not a fit for beginners |
Section 03Step 1. Account and plan
If you already have a Claude account with Pro, skip ahead to step 2. If not, let's go in order.
Sign up at claude.ai
Open claude.ai and sign in with Google or with your email. It takes a minute. You may be asked to confirm a phone number, which is normal.
Subscribe to Pro
The Code tab only works on a paid plan, so there's no point going further without one. In your account settings, pick the Pro plan, which is more than enough for the first few weeks. Max is for people who work in Claude Code for hours every day, and Ultra is for the longest tasks. You can upgrade later with one click, so there's no reason to overpay on day one.
Remember which email you used
Sounds trivial, but it's the most common reason the app later says "no access." The app must be signed in to the exact same account that holds the subscription. Write it down if you juggle several addresses.
That's it, your account is ready. One subscription unlocks both the regular chat on claude.ai and Claude Code. There's nothing extra to buy, and they share the same usage limits.
Section 04Step 2. Install Claude Code
There's nothing separate to install for Claude Code: the Code tab already lives inside the Claude app. The whole setup takes about five minutes.
Download the app
Open the official download page at claude.com/download and grab the version for your system, Mac or Windows. Install it like any program: double-click the file, next, done.
Sign in to the same account
Open the app and sign in with the same email that has the subscription. The sign-in may open in your browser. The tab is called Code, and you'll find it at the top of the app's sidebar. That's Claude Code.
Button labels change from version to version now and then, so go by what a button does rather than its exact name. Stuck after signing in? Describe the problem in the chat inside the same app. For a one-off question, that's fine.
Section 05Step 3. Working folder and a new session
Claude Code works inside a folder. Everything it creates goes there, and everything in there, it can see. So the very first rule: one task, one separate folder. Don't open it on your desktop or in your Documents folder where your whole life lives. Create an empty folder with a clear name, like "personal-site" or "sales-review."
Create an empty folder
Right-click on your desktop or in Documents, choose "New Folder," and give it a name. For example, my-site.
Start a new session and pick the folder
A conversation in the Code tab is called a session. Start one with the New or New session button. Where you choose the environment, keep Local: it means Claude works on your computer. Next to it is the folder picker. Choose my-site.
Switch to Auto mode
The mode switcher sits right there, next to the input box. Pick Auto so Claude works on its own instead of stopping at every edit. More on that in step 5. If it asks for permission to change files in this folder, click Always allow: it's your folder and it's empty.
Now you're looking at an input box. You can type like you would in a messaging app. The hardest part is behind you. The fun part starts now.
Section 06Step 4. First task: a live dialogue
For your first run, pick a task whose result you can see with your own eyes in a couple of minutes. A one-screen personal site is perfect: you open it in the browser right away and understand how the whole thing works. Here's the full dialogue as it looks on screen, so you know what to expect.
Hi. I'm a therapist who works with anxiety in adults. Build me a one-screen personal site: my name, Anna Miller, one sentence about how I help, three short bullet points on "what people come to me with," and a "Book a session" button that opens my Telegram t.me/anna_psy. Calm, warm colors, beige and olive. Make sure it looks right on a phone too.
Got it. Here's the plan: I'll create an index.html file with the whole page, pick a warm beige and olive palette, and make the layout responsive for phones. Creating index.html. Done. The page is in the my-site folder. Double-click index.html and it'll open in your browser. Want me to add a photo or a pricing block?
Notice two things. First, it told you the plan and then did the work. Second, it didn't ask about every file, because Auto mode is on. The file is already in the folder, and all that's left is to look at it.
Double-click index.html and take a look. You'll probably want to change something. That's normal, that's the whole idea. Keep going in the same plain language:
Nice. Make the button bigger and olive. Change the line under my name to "Helping you stop living in anxiety mode." And add a line at the bottom: "First session is 30 minutes, free."
Made three edits to index.html: enlarged the button and made it olive, replaced the subheading, and added the first-session line at the bottom. Refresh the page in your browser.
That's the whole secret. You describe, it builds, you look and refine. Two or three rounds and the site is done. By the way, Claude Code can also help you put a page like this online if you ask, but that's the next step and needs your hosting access. For a full project from voice notes to a finished site, see building a site by voice with Claude Code.
The first message gave the "contractor" everything it needed: who you are, what kind of site, what text, where the button goes, which colors, and where people will view it. The more of those details you pack into the first message, the fewer rounds of edits. If you forget something, no big deal: it'll ask, or make its own call, and you'll adjust.
Section 07Step 5. Auto mode and the other modes
The thought that scares beginners most is "what if it deletes something." Here's how it actually works. The Code tab has several work modes, and the switcher sits next to the input box. These are the ones a beginner needs:
| Mode | How it behaves | When to use it |
|---|---|---|
| Auto | Works on its own and stops if something looks unsafe. A separate check watches its actions and blocks risky ones, like sending important data out | From day one, this is your main mode |
| Plan | Changes nothing, only explores and proposes a plan | Before a big task, to agree on the approach first |
| Manual | Waits for your answer before every edit and command | I don't recommend it: a big task turns into approving one step after another |
Anthropic is upfront that Auto lowers the risk without guaranteeing anything, so pair it with a separate folder and a copy of anything important.
I strongly recommend Plan mode for anything bigger than a one-page site. Turn it on, describe the task, get a plan of five to ten points, edit it in plain words ("drop point three, the site is one page"), and only then let it run. That way you don't burn your limits on work that went the wrong way.
Two more things take away almost all the fear. Esc or the stop button halts Claude Code mid-sentence when you see it heading the wrong way. The /rewind command, or Rewind to here on a message, takes the session back to an earlier point, before the bad edit. Think of it as "undo" in Word, but for the whole job at once.
Rolling back restores files that Claude Code itself changed. If it ran a program that sent an email or published something online, that can't be undone. So for tasks where something leaves your computer, ask it to show you exactly what will be sent first.
Section 08Step 6. Project memory: the CLAUDE.md file
Every new Claude Code session starts with a blank slate. It doesn't remember that yesterday you agreed on beige colors, or that you call the people you work with clients, not patients. So you don't have to explain it every time, the project has memory: a CLAUDE.md file in your working folder. Claude Code reads it on its own at the start of every session.
Setting up memory is easy: write "create CLAUDE.md and note what this project is about." After that you can add to it in ordinary words, right in the session:
Save this to CLAUDE.md: this is the site of therapist Anna Miller. Palette is beige and olive. Address the reader as "you," warm and direct. Buttons always open Telegram t.me/anna_psy. Before big changes, show me the plan first.
It adds these rules to the file, and tomorrow, when you open the same folder, you pick up right where you left off. What's usually worth saving to memory:
- who you are and what you do, in a sentence or two;
- who the project is for and what tone it has;
- colors, fonts, contacts, and links that keep repeating;
- rules like "don't delete old versions, move them to an archive folder";
- mistakes it has already made and shouldn't repeat.
The last one is the most valuable. Every time you correct Claude Code, say "remember this in CLAUDE.md." A month later you'll have an assistant that knows your habits better than a new hire.
Section 09Cheat sheet: Code tab buttons and commands
Almost everything in the Code tab is a button next to the input box. Commands start with a slash and go right into the box, and typing / shows the list. Here's what will cover your first months.
| Button or command | What it does | When you need it |
|---|---|---|
| New or New session | Starts a new session | Moving on to a new task |
| Model picker next to the input box | Switches the model | Hard task that needs Opus, or a simple one where a fast model is enough |
| Mode switcher | Turns on Auto, Plan, or Manual | Turning on Plan before a big task |
| Usage ring next to the model picker | Shows how much of your plan's limit is used | Checking whether a big task will fit |
| Sessions list on the left | Brings back a previous session | You want to continue yesterday's work |
| The + button | Attaches a file to your message | You need to show it a file from another folder |
| Esc or the stop button | Stops the current action | You see it heading the wrong way |
/rewind or Rewind to here | Rolls back to an earlier message | An edit went badly |
/compact | Squeezes a long conversation into a short summary | The session is long and answers got worse |
Two more tricks make life much easier. The @ symbol plus a file name points Claude Code at a specific file: "look at @price.xlsx and total the revenue." And you can simply drag a screenshot into the window or paste it from the clipboard, and it will see the image. That's a lifesaver when it's easier to show an error than to describe it.
Models are simple. For everyday work, use Sonnet 5.5: it's a sensible balance of speed, quality, and limit usage. For hard tasks that need a lot of thinking, switch to Opus 5.5 in the model picker next to the input box. Light errands like "rename these files" are easy work for the fast Haiku 5.5.
Section 10How to give tasks: a formula and 12 ready phrases
Claude Code is exactly as good as your task is clear. People who say "nothing works" write something like "make me a nice website" nine times out of ten. That's like walking up to a designer and saying "just make something." They will. Something.
I use a simple four-part formula. Keep it in front of you for the first few weeks.
- Who I am and why. "I'm an English tutor and I need a page for parents."
- What already exists. "The folder has my prices in price.xlsx and three testimonials in reviews.txt."
- What the result should be. "One page: who I am, prices from the price list, testimonials, and a booking button."
- Constraints. "No animations, large font, must open fine on a phone."
And here are twelve phrases you can copy and fill in with your own details. Each one has been tested on real tasks.
- "First look through the folder and tell me what's in it. Don't change anything."
- "Show me a step-by-step plan. I'll approve it, then go."
- "Ask me whatever questions you need to do this well."
- "Build a one-screen personal site: [who you are, how you help, where the button goes, colors]."
- "Look at the export @sales.csv and calculate revenue by month, the top 10 clients, and the average order value. Save the result to a report.xlsx spreadsheet."
- "Sort all the photos in this folder into subfolders by the year and month they were taken. Don't delete anything."
- "Rename every file in the folder using the pattern date-title. Show me the list of new names first."
- "Turn my notes in the notes folder into one guide in Word with a table of contents."
- "Make a page with a booking form: name, phone, preferred time. Save submissions to a file."
- "Check this site for problems: broken links, typos, how it looks on a phone."
- "Explain in plain words what you just did and which files you changed."
- "Save what we just decided to CLAUDE.md."
I especially recommend the third one. When you're not fully sure what you want, ask Claude Code to question you. It'll ask about your audience, colors, copy, and where to send people, and after five answers the task gets several times clearer. More ways to talk to AI are collected in the AI prompt library.
A long task is easier to dictate. Turn on dictation on your computer (on a Mac, press Fn twice; on Windows, Win + H) and describe the task the way you'd explain it to an assistant out loud. Claude Code handles conversational speech, false starts, and "so, basically" just fine. Plenty of my clients work exactly like this: talk for a couple of minutes, get the result.
Section 11Five first projects by profession
So you're not staring at an empty input box, here are first-project ideas for people who sell services, courses, and consulting. Each takes one evening and brings real value.
| Who you are | First project | What to tell Claude Code |
|---|---|---|
| Therapist, coach | A booking page for a first session | "Build a page: who I am, what I work with, how a session goes, a booking button that opens Telegram" |
| Tutor | A lesson and payment tracker in a spreadsheet | "Make a spreadsheet: name, subject, schedule, paid or not, monthly total" |
| Nutritionist, trainer | A meal plan or program generator into a document | "From the recipes in this folder, build a weekly menu as a PDF with one combined shopping list" |
| Online school | A sales report from an export | "Using @orders.csv, total sales by product and month, build a chart, and save the report" |
| Freelancer, designer | Order in your project archive | "Sort this folder by client and year and list every project in a spreadsheet" |
Notice that not one row says "write code." You describe the result the way you'd describe it to an office assistant. Once you feel confident, move on to bigger tasks: a Telegram bot that answers common questions (walkthrough in a Telegram bot without a programmer), or connecting your own tools through MCP, covered in MCP in Claude. For the big picture on building things by conversation, read the piece on vibe coding.
One client, a sales mentor, started with exactly a spreadsheet. First he asked Claude Code to pull every lead from his message history into it, then to calculate conversion from lead to payment, then to chart it week by week. Three evenings later he had his own small analytics setup that he'd been planning to hire a contractor for. And the main thing, in his words: "For the first time I saw at which step people drop off."
Section 12When something goes wrong
Every beginner hits the same snags. I've collected them in one place so you don't have to dig through forums.
Nine times out of ten you're signed in to a different account than the one with the subscription. Sign out, sign back in with the right email, and restart the app. If it says the account has no access, check that your plan is active.
That means this account is still on the free plan. Go back to step 1 and check that you signed in with the email that has the subscription.
That's completely normal. Allow it and Claude installs it itself. If the app itself won't start without Git, update the app.
Press Esc if it's still working. Then type /rewind or pick Rewind to here on the message you want to go back to, to the moment before the bad edit. Then rephrase the task more concretely, or turn on plan mode and agree on the approach first. Scolding it with "you ruined everything" is useless. Calmly describe what you need instead.
The conversation is too long, and a lot of clutter has piled up in its working memory. Type /compact to shrink the conversation, or start a new session. Before that, ask it to save the important agreements to CLAUDE.md so they don't get lost.
The file is most likely in another folder. Claude Code sees the folder you picked for the session and everything inside it. Move the file into that folder, or start a new session with the right one.
Your plan has a short-window limit and a weekly limit. Wait for the window to reset, and it will tell you when. How to stretch your limits is covered in the next section.
Take a screenshot, drag it into the Claude Code window, and write: "This is how it looks on my end, fix it." A picture explains the problem better than any description. Do the same with any error on your screen.
The general principle: show any confusing message to Claude itself, in Claude Code or in the regular chat. It's better at untangling its own errors than any forum. For a big rundown of typical mistakes with AI, see beginner mistakes with AI.
Section 13Usage limits and how to stretch them
On Pro you don't pay per request, but it isn't unlimited either. There's a limit over a few hours and a weekly limit. Claude Code uses noticeably more than the regular chat, because it reads files, tries things, and checks its own work. For tasks like "personal site, spreadsheet, report," Pro is plenty. Once you're spending several hours a day in Claude Code, take a look at Max.
Here's what actually saves limits:
- One task, one session. Finished the site? Start a new session and do the sales report on a clean slate. A long conversation drags all the previous text along and costs more.
- The right model. Sonnet 5.5 for everyday work, Opus 5.5 only for genuinely hard stuff, Haiku 5.5 for small errands.
- Plan before a big task. Agreeing on the approach in words is cheaper than redoing finished work.
- Small folders. Don't open Claude Code in a folder with thousands of files, it will try to study them. A dedicated folder per task saves both time and limits.
- A precise task the first time. Every "no, not that" round costs limit. The four-part formula pays for itself right here.
Check what's left with the usage ring next to the model picker. If you want a broader overview of which AI tools to use for which tasks and what they cost, see the best AI tools of 2026.
Section 14Safety: five simple rules
Claude Code gets access to your computer, so a little hygiene doesn't hurt. The rules are simple and easy to follow.
- A separate folder for every task. Never launch it at the root of your drive or in the folder with all your documents.
- Auto mode. Claude works on its own and stops if something looks unsafe. If you don't understand an action it suggests, ask: "Explain in plain words what you want to do."
- Don't type passwords or keys into the chat. If it needs access to a service, ask Claude Code where to store the key safely, and put it there yourself.
- Back up anything important. Working with valuable files? Copy the folder first. Two seconds, and you'll sleep better.
- Check everything that goes out. Numbers in a report, links on a site, the text of an email campaign. Final review is on you, especially where money and client data are involved.
It sounds stricter than it is. A separate folder, Auto mode, and a copy of anything important take ten minutes on day one, and a beginner's fear is always bigger than the real risk.
Section 15The whole path in one minute
Let's run through the essentials so it all clicks into one picture.
- You need a computer, the Claude app, and a Pro, Max, or Ultra plan.
- Work in the Claude app, in the Code tab: if the account gets blocked, your files stay in your folder.
- Create a separate empty folder for each task and pick it in a new session.
- Keep the first task small and visible: a personal site, a spreadsheet, a report. Use the formula: who you are, what exists, what result you need, constraints.
- Switch to Auto, use Plan before a big task, and undo a bad step with
/rewind. - Ask Claude to set up a CLAUDE.md file and add everything you agree on.
- One task, one session, Sonnet 5.5 for everyday work. That way your limits last a long time.
That's it. Honestly, the hardest part of Claude Code is deciding to open it for the first time. After that you talk and it does the work. Pick one small task that's been hanging over you and get it done tonight. Ready to try? 🙂
FAQFrequently asked questions
How do I use Claude Code if I'm not a programmer?
The same way you'd give tasks to an assistant. Open the Code tab in the Claude app, pick a separate folder, and describe the result in plain words: who you are, what needs to be done, how it should look. It writes all the code itself. Your job is to check the result and ask for changes.
Can I use Claude Code for free?
No. On the free plan, the Code tab asks you to upgrade. Claude Code comes with Claude Pro ($20 a month, or $17 a month billed yearly), Max ($100 a month), and Ultra ($200 a month). Pro is enough for a beginner.
Where is it easiest for a beginner to use Claude Code?
In the Claude app for Mac or Windows, on the Code tab: you pick a folder with your mouse and type the task. I recommend working only there. If your account ever gets blocked, your chats go with it, but the files stay in the folder on your computer.
Do I need to install anything to use Claude Code?
Just the Claude app. Download it from claude.com/download and install it like any program. The Code tab is already inside, and nothing else needs installing.
Can Claude Code delete my files?
Any tool that touches files carries some risk. Work in a separate folder, use Auto mode, where Claude stops if something looks unsafe, and keep a copy of anything important. A bad edit can be rolled back with the /rewind command.
What is CLAUDE.md and why do I need it?
It's the project memory file in your working folder. Claude Code reads it on its own at the start of every session, so it's the place for your rules: who you are, colors, contacts, agreements. You create it and add to it by saying "remember this in CLAUDE.md."
Which model should I choose in Claude Code?
Sonnet 5.5 for everyday work: it balances quality, speed, and limits. For hard tasks, switch to Opus 5.5 in the model picker next to the input box. For simple errands, the fast Haiku 5.5 is enough.
What do I do when I run out of limits?
Wait for the window to reset, and Claude Code will tell you when. To make limits last longer, keep one task per session, work on Sonnet 5.5, and agree on a plan in Plan mode before big tasks. If you keep running short, move to Max.
Does Claude Code understand plain everyday language?
Yes, very well. Type or dictate tasks the way you'd say them to a person, in English or many other languages, and it answers in kind. A few commands like /rewind and /compact are fixed words, and they're in the cheat sheet above.