Bonus 1. The thing you have been avoiding. It takes about fifteen minutes to stop being scary forever, and everything else in this session sits on top of it.
In the main course you dragged a file into Claude and it built you a studio.
It did that by using a terminal. You watched the output scroll past. You have already been in the room, you just were not the one talking.
A terminal is a window where you type the name of a thing you want done, instead of hunting for a button that does it.
That is the whole idea. Everything else is vocabulary.
Because it works, and because it is the one interface that has never broken compatibility.
A button can only do what someone drew a button for. A typed instruction can be combined, repeated, scheduled, and given to a machine to run at 3am. That is not nostalgia, it is the reason the unattended queues in Module 4 are possible at all.
Mac: press Cmd then Space, type terminal, press Return.
Windows: press Win, type terminal, press Return.
A window appears with some text and a blinking cursor. Nothing has happened. It is waiting.
Nothing you type here does anything until you press Return. You can type nonsense and delete it. The window is not armed.
That text before the cursor is the terminal telling you two things: who you are and where you are standing.
sean@macbook ~/Documents/my-film %Your name, your machine, the folder you are currently inside, and then a symbol that means "go ahead."
It is a status bar, not a command. You never type it.
You are always inside a folder. Everything you type happens to that folder unless you say otherwise.
This is exactly like the Finder or File Explorer, except instead of seeing the folder, you are standing in it.
| Type this | It means |
|---|---|
pwd | where am I standing right now |
ls | what is in here |
cd films | walk into the folder called films |
Try all three. Then cd .. which means walk back out one level.
Type cd (with the space) then drag a folder from your Finder window into the terminal. It fills in the path for you. Nobody types long paths by hand, including people who have done this for twenty years.
~ symbol~ means your home folder. ~/Documents/my-film means Documents, then my-film, inside your home.
That is all it is. A shortcut so nobody has to write /Users/yourname/ a hundred times a day.
You will not, with what you have been taught here. pwd, ls and cd only look. None of them can change a single file.
The commands that change things are a different, small set, and you will always know when you are using one because you will have typed the word yourself.
The genuine danger is a command someone else gave you that you do not understand. That is a real risk and it has a real answer, on the next slide.
Paste it into Claude before you paste it into a terminal.
"Explain exactly what this command does, in plain English, line by line. Tell me specifically whether it deletes, overwrites or sends anything anywhere, and what folder it will affect."
This is not a beginner's crutch. It is what a careful professional does, because the cost of being wrong is asymmetric and the check takes four seconds.
Some things are genuinely not undoable, and your studio already guards the worst of them. From the main course you have a delete guard and a secret guard, and you watched one refuse a command.
Two habits close the rest of the gap:
| Key | What it does |
|---|---|
| Ctrl C | stop whatever is running, right now |
| Ctrl L | clear the screen, changes nothing |
| Up | bring back the last thing you typed |
| Tab | finish the name you started typing |
Ctrl C is the one to remember. If anything ever runs longer than you expected, that stops it. It is the escape hatch and it always works.
Start typing a folder name, press Tab, and the terminal finishes it.
It also proves the thing exists. If Tab does not complete it, you have the name wrong, and you found out before you pressed Return rather than after.
You are learning it so you understand what you are looking at while it types them.
The tool runs the commands. You need to be able to read the room, not do the work.
When it says it is running something in ~/Documents/my-film, you know:
ls is it looking, not changingThat is the whole difference between supervising and hoping.
This is the one thing worth being able to do yourself:
cd ~/Documents/my-film
claudeWalk into the project, then start it there. That is how it knows which folder is its world, which was the very first idea in Module 0 of the main course.
Starting it in your home folder instead of your project is the most common beginner mistake. It then has your entire computer as its world, which is both slower and less safe.
Ten minutes. Nothing here can change a file.
pwd. Read where you are.ls. Read what is there.cd and drag one of your project folders in. Press Return.pwd again. You moved.ls. That is your project, seen from the inside.cla then press Tab. Watch it finish.claude. You are in, standing in the right folder.The window is not for programmers. It is a room where you say what you want.
The File That Tells It Who You Are. One file in your project that it reads every single time, and why it is the highest-leverage thing you will ever write.
Verified against Claude Code 2.1.220 · 2026-07-30.