You’ve now used Claude Code entirely through the app — open a folder, type in the chat, click to approve. No terminal anywhere. That’s the whole point of the Desktop path: you don’t need one.
But you’ll hear the word constantly, so let’s deflate it.
A terminal is just a text-only way to talk to your computer. Instead of clicking icons, you type a command and press Enter. Same computer, same files — different way in.
You already know the graphical way: you double-click a folder to open it, drag a file to move
it, click the back arrow to go up a level. A terminal does all of that too, except you type
short commands instead of clicking. When you open one, it shows a small prompt — usually
ending in a $ — that means “I’m waiting, type something.”
When you’d actually open one
For everything in this course, you won’t have to. The reasons people reach for a terminal anyway:
- Linux. The Claude desktop app is Mac and Windows only, so on Linux the terminal is how you run Claude Code.
- Automation and scale. Once you want Claude to run on a schedule, plug into other developer tools, or repeat a task a thousand times, the terminal is where that lives.
- You just prefer typing. Some people are faster with their hands on the keyboard.
If that’s you — or you’re on Linux — that’s the Power Track: Level 11 — Terminal & Automation. It teaches the terminal properly, from “how to open one” onward. It’s optional for everyone else, and you can come back to it any time.
For now, you don’t need it. The app has everything your first real work requires.
What’s next
That’s Level 1. You can install Claude, sign in, hold a conversation, see what it sees, and approve what it does — all from the app. Next, Level 2 gives you the words for the world Claude works in.