Start here · Lesson 1.1
Claude Code Tutorial: AI That Works on Your Computer
Most people use AI like a search box with manners. They type a question, copy the answer, paste it somewhere, and repeat. It works, but you are the one doing all the carrying.
Claude Code is a different kind of tool. Anthropic's documentation describes it as an agentic coding tool that reads your files, edits them and runs commands. It works from your own computer, so it can open your files, make new ones, run things and fix what breaks. This tutorial explains what that means in practice and shows you how to give it a first real job.
A chat window gives you advice you then act on. Claude Code acts on your computer for you, inside a folder you choose, and tells you what it did.
Chat versus a tool that works
In a chat, the AI cannot see your files. You describe them, or paste pieces in, and it answers from what you gave it. Anything it makes lives in the chat until you copy it out.
Claude Code starts in a folder on your machine. It can read what is there, write new files, and run commands, asking you first in manual mode. If you ask for a landing page, you get a real file in that folder. If you ask it to tidy a messy folder, it moves the files itself.
| Chat window | Claude Code | |
|---|---|---|
| Sees your files | Only what you paste | The folder you open it in |
| Makes files | Text in the chat | Real files on your computer |
| Remembers you | Depends on the app and its settings | Can, through a notes file called CLAUDE.md |
| Who does the carrying | You | It does |
What it can do for a non developer
Anything digital is fair game. In the Halftime lesson on this, the examples are cleaning up a messy desktop and drives, building a website or landing page, planning social posts, clearing an inbox and drafting replies, building dashboards from your numbers, and making slides and documents.
You do not need to know how to code to ask for these. You describe the result in plain words and review what comes back, the way you would with a capable assistant.
What you need before you start
- A Mac running macOS 13.0 or later, which is the minimum in Anthropic's setup docs. Windows is supported too, but the steps in the lesson use a Mac.
- An account that can use Claude Code. The quickstart lists a Claude Pro, Max, Team or Enterprise subscription, a Claude Console account, or access through a supported cloud provider. Check Anthropic's site for the current details, as they change.
- A folder with something real in it. A project, a pile of documents, a half built page.
Your first session
- Install itFollow the install steps in our 6 step Mac setup guide. It is a one time job.
- Open the right folderUse Terminal to go to the folder you want it to work in, then start Claude Code there. That folder is its working directory, so keep the job pointed at it.
- Ask for a small, real jobFor example, "Look at this folder and tell me what is in it, then suggest a tidy structure. Do not move anything yet."
- Read before you approveIn the default manual mode it asks permission before it edits files or runs most commands. Read each request. Say no when you are unsure. Newer versions can start in other permission modes, so check which one you are in.
- Ask what it didEnd with "Summarise every change you made." Keep that summary.
Why the first job should be a read only one
Begin by asking it to look and report. You learn how it thinks, you see how it describes your folder, and nothing can go wrong. Once the report matches reality, ask for a small change in a copy of the folder.
This is the same habit you would use with a new hire. You do not hand over the keys on day one. You give a small task, check it, then give a bigger one.
Three mistakes beginners make
Treating it like a chat. If you paste text into it and ask for advice, you are paying for a hammer to use as a paperweight. Point it at files and ask it to do something.
Giving it a vague job. "Make my site better" gets a vague result. "Change the headline on index.html to this, and keep everything else" gets a precise one. For a fuller method, read how to brief AI like a senior hire.
Skipping the permission prompts. Each prompt is a chance to catch a mistake. Read them until you trust the pattern of what it asks for.
Keep sensitive things out
Do not put passwords, bank logins or private keys in the folder you open. If a job needs one, handle that step yourself. Everything else is fair to share, because the point is that it can see your real work.
Where this leads
Once the basics feel normal, the gains compound. You can give it a memory so it stops starting from zero, connect it to your email, and teach it rules once so it follows them every time. Each of those has its own guide, and the Halftime lesson covers the whole path in 26 minutes with the screen shown.
A worked example: tidy a downloads folder
Say your Downloads folder holds a few hundred files with names like "final2" and "scan0043". Here is how the first session could go. You open Claude Code in that folder and ask: "List the types of files here and group them by what they seem to be. Do not move anything." You read the list. It suggests folders for invoices, photos, documents and installers.
Next you ask it to make a copy of the folder first, then move the copies into the new structure and write a short note listing where everything went. You open the copy, check a handful of files, and only then decide whether to do the same in the original. Nothing here needs code knowledge. It needs clear instructions and a habit of checking.
How to word a job so it works
A good request has a place, an action and a limit. The place is the folder or file. The action is what you want done. The limit is what it must not touch. "In the folder called website, change the phone number on the contact page to this one, and leave every other file alone" has all three.
When a result is off, say what is wrong in plain words and ask again. You are not failing at the tool. Iteration is the normal way to use it, and each round gets closer.
Signs you are using it well
You are using it well when you are mostly reviewing rather than copying. You can name the folder it is working in. You know what the last three things it changed were. You have started saving instructions you reuse. If you are still pasting long text in and copying long text out, go back to the first section and point it at real files.
Questions people ask
Do I need to know how to code to use Claude Code?
No. You describe the result in plain words and review what it does. Reading a little of what it shows you helps, but it is not required.
Is Claude Code the same as the Claude chat app?
No. They are separate products from Anthropic. Claude Code works with your files and commands, while the chat app works with what you type or upload. Claude Code can also be used in the desktop app, in editors and on the web, so check the overview page for the option that suits you.
Is it safe to let AI change my files?
In manual mode it asks for permission before editing files or running most commands, and you can say no. Start in a copy of a folder and keep backups of anything you cannot replace.
What should I ask it first?
Ask it to look at a folder and describe what it finds, without changing anything. Then move to one small change.
Next step
Watch the whole setup done on screen in Lesson 1.1, then run your own first job the same day.