What is the terminal, and where do I actually find it?

What it actually is

The terminal is a window where you talk to your computer by typing, one line at a time, instead of clicking icons and menus. You type a command, press Return (macOS) or Enter (Windows), and the computer prints its answer below and waits for your next line.

Three words get tangled together here, so it’s worth separating them once. The terminal is the app itself: Terminal on a Mac, Windows Terminal on Windows. Inside that window runs a shell, the program that actually reads what you type and carries it out, usually zsh on a modern Mac or PowerShell on Windows. CLI, short for command line interface, just names this whole style of working: typing instructions instead of pointing at buttons. Apple’s own documentation describes Terminal as “an app you use to perform tasks using a command line interface (CLI) in macOS,” which covers the whole naming tangle in one line.

The closest working analogy is a text conversation with your computer’s operating system: it does exactly what you type, nothing more forgiving than that, and forgets it all once you close the window. If a guide mentions WSL on Windows, that’s a separate Linux environment running inside Windows with its own terminal setup; most vibe coding tools never ask you to touch it.

Why your AI just did this

Your agent lives in the terminal because that’s where many tools only exist. Cursor and Claude Code both build in a terminal panel so the agent can run real commands and show you the live output, instead of describing what it did in a chat bubble. When your agent scaffolds a new app, it types npm install in that window and reads back what comes out.

Tutorials send you there for the same reason. Cloning a project, installing its dependencies, and starting a local dev server all happen at this prompt, not through a graphical installer. Next.js, Vite, and most JavaScript starters assume you’re fine typing four or five commands, even though normal computer use never required it.

When you’ll run into it

The classic moment: a guide says “open your terminal and run npm install,” and you don’t know what that means or where to click. Find it on a Mac in Applications then Utilities, or via Spotlight (Cmd+Space, type Terminal). On Windows 11, Windows Terminal is the default, so search “Terminal” from the Start menu.

Once it’s open you’ll see a prompt: a line ending in %, $, or > that waits for you. On macOS with zsh it might read yourname@MacBook project %; on Windows PowerShell, PS C:\Users\yourname>. Whatever comes before that symbol is the folder your next command acts on.

From there, a small set of commands covers most of what a vibe coder ever types: cd to change into a folder, ls on Mac (dir on Windows) to list what’s inside it, npm install to download a project’s dependencies, npm run dev to start the local server you preview your app on, npx to run a tool without installing it first, like npx create-next-app@latest, and git to work with your project’s history, starting with git clone and git status.

What to check

• Confirm you’re opening the right app: Terminal (Applications, Utilities) on Mac, Windows Terminal (search “Terminal”) on Windows, or your editor’s built-in terminal panel
• Read what comes before the prompt symbol before you type; if a command fails with “no such file or directory,” cd into the right folder first
• Never run a command you can’t restate in one sentence. Ask your agent what a command does and what could go wrong before you paste it, especially anything starting with sudo
• If a command replies command not found, that’s your PATH variable not knowing where to find the program, not you typing it wrong
• Getting Permission denied (see permission denied) means the operating system is blocking the action, not that the command is broken. Don’t reach for sudo and chmod as a reflex; ask what’s actually being blocked and why, since both can change permissions more broadly than you meant
• If your app runs at a localhost address after npm run dev, that number after the colon is a port, not part of the web address itself

Say it like a dev

Instead of: “the terminal thing isn’t working” Say: “I ran npm install and got this error: [paste it exactly]. What’s failing and how do I fix it?”

Instead of: “it says permission denied, should I just use sudo” Say: “I’m getting Permission denied on this command. What’s actually blocking it, and is sudo the right fix or a workaround that hides the real problem?”

Instead of: “I don’t know what this command does, should I just run it” Say: “Explain what this command does, line by line, before I run it, especially any part with sudo or rm.”