What is a terminal? — CBW Foundations #01

// THE SHORT ANSWER

A terminal is a text-only way to talk to your computer.

Instead of clicking icons, you type a sentence and press Enter. The computer reads the sentence, does the thing, and prints a reply. That's it. Everything else in this article is just teaching you the sentences.

Last year I opened Terminal on my Mac for the first time, stared at the blinking cursor for about 30 seconds, then closed the window and went back to building things in Notion. I was a designer. I had no business in there. That was wrong.

Every AI tool in the guides on this site — Whisper, Llama, Stable Diffusion, the whole zoo — starts with one line typed into a terminal. If you don't know what a terminal is, you can't run any of them. So this is the first thing to fix.

Good news: the terminal is the simplest piece of software on your computer. It does one thing — it reads what you type and shows what happens. There are no menus. There is no autocorrect (well, almost none). It can't surprise you. By the end of this article you will have run your first command and the black window will have lost its teeth.

// 01What it actually is

Forget every movie hacker scene you've ever watched. A terminal is a text chat window between you and the operating system. You type one line. You hit Enter. The OS reads the line, does what you asked, and prints the result. Then it waits for your next line.

That's it. The whole abstraction. No more mystery.

// the way you usually do it

Mouse + windows

// the way builders do it

Terminal

You see icons and menus.

You see a blinking cursor.

You point, you click.

You type a sentence.

Each app shows you its own controls.

Every app shares one input box.

Easy to learn. Slow to repeat.

Steep at first. Then very fast.

Hard to share with a friend ("first you click the…").

Easy to share — it's just text. Paste this, press Enter.

When an AI guide tells you to run something, this is the window they mean. "Run" just means: paste the line, press Enter, watch what happens.

// 02How to think about it

Picture a very polite robot sitting behind a tiny window. You slide a note under the window. The robot reads it, walks off to do the thing, and slides back a reply. Then it sits down again and waits.

// The whole loop, every single time

You type

one line of text

Computer reads

the line you typed

Computer does

the thing, prints reply

This loop never changes. Whether you're installing Whisper, deleting a folder, or asking Git what changed today — it's type, Enter, read. The hard part isn't the loop. The hard part is learning which sentences to type.

// 03The four words you actually need

Every guide uses the same four words. Learn them once, you'll never re-learn them.

Prompt

The character that says type now. Usually $ or % or >. Already covered above — moving on.

Command

The sentence you type. ls is a command. brew install ffmpeg is a command. A command is usually one short verb followed by stuff that verb needs. ls means "list." brew install ffmpeg means "hey brew, install ffmpeg."

Output

Everything the computer prints back after you hit Enter. The transcript. The error message. The little bar chart of download progress. All of it is output. Output is information, even when it looks like nonsense.

Working directory

The folder your terminal is currently "inside." Every command runs relative to this folder. If you type ls, you get the files in this folder, not your whole computer. You move between folders with cd ("change directory"). The current folder is usually written in your prompt — that's the ~ part.

// 04Your first command, demonstrated

Here is what a real terminal session looks like. You don't have to type along yet — just read it. We'll do the typing in the next section.

The user types ls (lowercase L, lowercase S). That's the command for "list everything in the current folder." The computer prints the list, then drops back to a fresh prompt waiting for the next command.

Terminal · ~/projects

# you are inside the projects folder

$ls

cbw-site

voice-clone

whisper-tests

notes.md

# the prompt comes back. your turn again.

Notice the pattern: type, Enter, output, prompt comes back. That's the rhythm. If the prompt doesn't come back, the computer is still working — let it cook.

Three more commands worth knowing today

pwd — print working directory. Tells you which folder you're in. Useful when you're lost.
cd Downloads — change directory to Downloads. Switch folders. cd .. goes up one folder.
echo hello — echo just prints back what you give it. Useless on its own, but a great "is this thing on" test.

// 05Now you. Open a terminal and run one command.

Five minutes. No installs. By the end you will have used a terminal. Pick the lines for your OS.

// TRY IT — 5 minutes, no install

Open a terminal and run your first command

MACMac: Press ⌘ + Space. Type Terminal. Hit Enter. A black-ish window opens. Welcome.
WINWindows: Press the Windows key. Type PowerShell. Hit Enter. A blue window opens. (Don't use Command Prompt — PowerShell is the modern one.)
LINUXLinux: Press Ctrl + Alt + T on most distros, or open "Terminal" from the app menu.
Everyone: Type the letters ls (Mac/Linux) or dir (Windows). Press Enter. You should see a list of files — your home folder's contents.
Now type pwd and press Enter. It prints the full path to where you are. On Mac that's usually /Users/yourname.
Last one: type echo I am in the terminal and press Enter. It echoes you back. You just had a conversation with your computer.

Done? Close the window. You've now used a terminal. Every guide on this site starts from exactly here.

// READ NEXT3

ALL 5 →