🪜 The Tiny Pattern That Matters
You are not here to become a developer, or an IT person, or someone who suddenly falls in love with terminal windows. You are here to recognise one useful pattern so Module 4 does not feel like black magic.
That pattern is tiny: open the terminal, launch the tool, let it sign in, ask one prompt. That's it. No points for memorising extra commands. No need to get fancy.
What I care about in class: not whether you can recite commands from memory, but whether you recognise what is happening when the tool starts working from your machine.
Windows users: when this module says "Terminal", you'll use PowerShell or Windows Terminal — both come pre-installed on Windows 10/11. Not Command Prompt (cmd.exe), which is the older one. Open it by searching "PowerShell" or "Windows Terminal" in your Start menu. All the npm commands in this module work the same — the only difference is what the window looks like.
If you get a cannot be loaded because running scripts is disabled error when running npm, ask for help — it's a one-line PowerShell fix and you haven't done anything wrong.
Choose one term for each sentence, then check your thinking. The goal is not perfection first go. The goal is knowing what these words mean when they pop up in class.
“Before we do anything else, open the _____ on your laptop. That is the text window where we will paste a couple of commands.”
“Gemini and Claude Code are both examples of a _____: a tool you start from the terminal and then work with from there.”
“If a tool on your laptop sends a request away to another service in the background, it is using an _____.”
“If that service asks for a secret code to prove the request belongs to your account, that code is an _____.”
🚪 The Four Front Doors
There are four main ways to work with AI. You've been through the first one already. This module opens the second. The later modules take you further.
The AI moves from a server somewhere to your own machine. It can see your files, remember context across a whole project, and stay useful for work that doesn't fit in a single conversation window. One install command, one sign-in — and you're somewhere most people have never been. This is what today is about.
A visual build cockpit. You describe what you want made, point it at a folder, and watch it write, edit, and run code — while you watch, redirect, and steer. If the terminal is learning to drive, an agentic IDE is having a co-pilot who can read the whole map at once. The terminal skills from today turn into actual builds in Module 5.
Claude and ChatGPT as proper apps in your dock — one click away, always ready. Less friction than opening a browser tab, and they remember context better than a fresh window. Not the main skill we're teaching, but a perfectly good way to spend time with AI.
This is the main event. It is a simulator, so it will not touch your real machine. We are learning the sequence without the stress.
Raglan workshop path: start with Gemini first. It is the simplest path for most beginners and the one we use in class.
- Choose your computer type.
- Copy the Gemini install command.
- Launch the tool and finish the simulated sign-in.
- Ask one simple prompt in normal language.
Which computer are you on?
Best first run for class. Good if you already have a Google account and just want the cleanest on-ramp.
Not startedWorth comparing once the first path makes sense. Strong for file-aware work, but not the first hurdle I want beginners tripping over.
Not startedgemini to launch it. When the browser pops open asking you to sign in with Google, do that. Then try: "Kia ora. What can you help me do from here?" Once you get a response, you've done it.For Mac: if Terminal says command not found: npm, you need to install Node.js first — download it from nodejs.org and run the installer. If the install finished but gemini or claude still says not found, just close Terminal and reopen it — that refreshes the path.
🔑 Keys, Credits & Costs
You do not need to sort API keys or billing just to understand the workshop path. But if you want the official pages ready for later, here they are.
Beginner view: browser sign-in first, API keys later. Module 5 is about building, and Modules 7 and 8 are where you go deeper.
🩹 When Setup Gets Wobbly · Troubleshooting
Most issues here are setup wobbles, not signs that you are rubbish at computers. Click any one that sounds familiar.
npm is missing
Install Node.js from nodejs.org, then close and reopen the terminal.
The command still is not found
That usually means the install finished but your terminal session has not refreshed yet. Close it and open it again.
The browser login did not open
Run the launch command again. If needed, sign in to the provider site in your browser first, then relaunch the tool.
Windows blocked npm.ps1
That is a PowerShell policy issue, not you breaking anything. In class, ask for help rather than trying random fixes off the internet.
I do not want to pay yet
Sweet as. Start with the Gemini workshop path first. Leave API keys and paid stacks for later once the basic idea feels solid.
This still feels like a lot
Use a desktop app first, get comfortable there, then come back to the terminal. The point is confidence, not heroics.
▶️ Optional More Terminal Depth
This part is genuinely optional. If you can do the simulator flow, you know enough terminal for the workshop. These videos are here only if you want a fuller feel for the environment later on.
Safe to skip: this is background, not homework.
Mac Terminal for Absolute Beginners · Useful if you want more context beyond what we need for the workshop.
Windows Terminal for Beginners · Extra depth, not required for the class path.
Linux Terminal Basics · Background only if you want more later on.
Ka pai. That was enough terminal.
You do not need much more terminal theory than this for the workshop. The whole point now is to use the doorway: build something real next, then polish it, then choose a simple stack that keeps it useful.
Want to go further with the tools you just installed?