The terminal is a text box. That's the whole secret.

If you are starting here, the terminal is a text box on your machine: type a name, press enter, the computer does it.

If you already ran a studio on this path, you already shipped a tool in the browser. This chapter is the same work on your machine: a box where you type the name of a thing you want done, press enter, and the computer does it.

If the word "terminal" still means green text and a hoodie, that picture is doing you a disservice. The truth is boring in the best way.

The terminal is a text box. You type the name of a thing you want done. You press enter. The computer does it and tells you what happened. That is the entire idea. There is nothing else hiding behind it.

You already drive your computer every day. You click a folder, it opens. You drag a file, it moves. The terminal is the same set of actions with the mouse swapped out for words. "Open that folder" becomes cd. "Show me what's in here" becomes ls. Same computer, same files, different steering wheel.

Why bother, if the mouse already works

Fair question. Here's the honest answer.

• Every tool in the rest of this course assumes it. Installing the Claude CLI, running Python, using git. All of it happens in the terminal. This chapter is the door the other chapters walk through.

• It's faster once it's yours. Making twelve folders by hand takes twelve clicks and twelve typed names. In the terminal it's one line.

• It's repeatable. A click happens once and is gone. A typed command can be saved, shared, and run again. That's the whole reason developers and AI tools live here.

• The AI tools you're here to learn are terminal tools.

  The Claude CLI and the Codex CLI, the next two chapters, are programs you run by typing. You can't skip the room they live in.

What this chapter is not

It is not a deep dive. There are people who spend years getting good at the shell, and this chapter does not try to make you one of them. You will learn maybe eight commands. Eight is enough to get through this whole course and most of a real building job.

What you'll be able to do at the end

By the end of these three lessons you will have:

• Opened a terminal on your own machine, on purpose.
• Found out where you are in your files (pwd) and what's around you (ls).
• Moved into and out of folders (cd) using both the long way and the shortcuts.
• Made a folder (mkdir), made a file (touch), and read a file (cat).
• Understood what a "shell" is and why deleting things in the terminal has no undo, so you treat that one command with respect.

That's it. Three short lessons, about twenty-five minutes. After this, the Claude CLI chapter has somewhere to stand.

the Claude CLI chapter has somewhere to stand.

The terminal is a text box. That's the whole secret.

If you are starting here, the terminal is a text box on your machine: type a name, press enter, the computer does it.

If you already ran a studio on this path, you already shipped a tool in the browser. This chapter is the same work on your machine: a box where you type the name of a thing you want done, press enter, and the computer does it.

If the word "terminal" still means green text and a hoodie, that picture is doing you a disservice. The truth is boring in the best way.

The terminal is a text box. You type the name of a thing you want done. You press enter. The computer does it and tells you what happened. That is the entire idea. There is nothing else hiding behind it.

You already drive your computer every day. You click a folder, it opens. You drag a file, it moves. The terminal is the same set of actions with the mouse swapped out for words. "Open that folder" becomes cd. "Show me what's in here" becomes ls. Same computer, same files, different steering wheel.

Why bother, if the mouse already works

Fair question. Here's the honest answer.

• Every tool in the rest of this course assumes it. Installing the Claude CLI, running Python, using git. All of it happens in the terminal. This chapter is the door the other chapters walk through.

• It's faster once it's yours. Making twelve folders by hand takes twelve clicks and twelve typed names. In the terminal it's one line.

• It's repeatable. A click happens once and is gone. A typed command can be saved, shared, and run again. That's the whole reason developers and AI tools live here.

• The AI tools you're here to learn are terminal tools.

  The Claude CLI and the Codex CLI, the next two chapters, are programs you run by typing. You can't skip the room they live in.

What this chapter is not

It is not a deep dive. There are people who spend years getting good at the shell, and this chapter does not try to make you one of them. You will learn maybe eight commands. Eight is enough to get through this whole course and most of a real building job.

What you'll be able to do at the end

By the end of these three lessons you will have:

• Opened a terminal on your own machine, on purpose.
• Found out where you are in your files (pwd) and what's around you (ls).
• Moved into and out of folders (cd) using both the long way and the shortcuts.
• Made a folder (mkdir), made a file (touch), and read a file (cat).
• Understood what a "shell" is and why deleting things in the terminal has no undo, so you treat that one command with respect.

That's it. Three short lessons, about twenty-five minutes. After this, the Claude CLI chapter has somewhere to stand.

The terminal is a text box. That's the whole secret.

If you are starting here, the terminal is a text box on your machine: type a name, press enter, the computer does it.

If you already ran a studio on this path, you already shipped a tool in the browser. This chapter is the same work on your machine: a box where you type the name of a thing you want done, press enter, and the computer does it.

If the word "terminal" still means green text and a hoodie, that picture is doing you a disservice. The truth is boring in the best way.

The terminal is a text box. You type the name of a thing you want done. You press enter. The computer does it and tells you what happened. That is the entire idea. There is nothing else hiding behind it.

You already drive your computer every day. You click a folder, it opens. You drag a file, it moves. The terminal is the same set of actions with the mouse swapped out for words. "Open that folder" becomes cd. "Show me what's in here" becomes ls. Same computer, same files, different steering wheel.

Why bother, if the mouse already works

Fair question. Here's the honest answer.

• Every tool in the rest of this course assumes it.

  running Python, using git. All of it happens in the terminal. This chapter is the door the other chapters walk through.

• It's faster once it's yours. Making twelve folders by hand takes twelve clicks and twelve typed names. In the terminal it's one line.

• It's repeatable. A click happens once and is gone. A typed command can be saved, shared, and run again. That's the whole reason developers and AI tools live here.

• The AI tools you're here to learn are terminal tools.

  The Claude CLI and the Codex CLI, the next two chapters, are programs you run by typing. You can't skip the room they live in.

What this chapter is not

It is not a deep dive. There are people who spend years getting good at the shell, and this chapter does not try to make you one of them. You will learn maybe eight commands. Eight is enough to get through this whole course and most of a real building job.

What you'll be able to do at the end

By the end of these three lessons you will have:

• Opened a terminal on your own machine, on purpose.
• Found out where you are in your files (pwd) and what's around you (ls).
• Moved into and out of folders (cd) using both the long way and the shortcuts.
• Made a folder (mkdir), made a file (touch), and read a file (cat).
• Understood what a "shell" is and why deleting things in the terminal has no undo, so you treat that one command with respect.

That's it. Three short lessons, about twenty-five minutes. After this,

The terminal is a text box. That's the whole secret.

If you are starting here, the terminal is a text box on your machine: type a name, press enter, the computer does it.

If you already ran a studio on this path, you already shipped a tool in the browser. This chapter is the same work on your machine: a box where you type the name of a thing you want done, press enter, and the computer does it.

If the word "terminal" still means green text and a hoodie, that picture is doing you a disservice. The truth is boring in the best way.

The terminal is a text box. You type the name of a thing you want done. You press enter. The computer does it and tells you what happened. That is the entire idea. There is nothing else hiding behind it.

You already drive your computer every day. You click a folder, it opens. You drag a file, it moves. The terminal is the same set of actions with the mouse swapped out for words. "Open that folder" becomes cd. "Show me what's in here" becomes ls. Same computer, same files, different steering wheel.

Why bother, if the mouse already works

Fair question. Here's the honest answer.

• Every tool in the rest of this course assumes it.

  running Python, using git. All of it happens in the terminal. This chapter is the door the other chapters walk through.

• It's faster once it's yours. Making twelve folders by hand takes twelve clicks and twelve typed names. In the terminal it's one line.

• It's repeatable. A click happens once and is gone. A typed command can be saved, shared, and run again. That's the whole reason developers and AI tools live here.

• The AI tools you're here to learn are terminal tools.

  The Claude CLI and the Codex CLI, the next two chapters, are programs you run by typing. You can't skip the room they live in.

What this chapter is not

It is not a deep dive. There are people who spend years getting good at the shell, and this chapter does not try to make you one of them. You will learn maybe eight commands. Eight is enough to get through this whole course and most of a real building job.

What you'll be able to do at the end

By the end of these three lessons you will have:

• Opened a terminal on your own machine, on purpose.
• Found out where you are in your files (pwd) and what's around you (ls).
• Moved into and out of folders (cd) using both the long way and the shortcuts.
• Made a folder (mkdir), made a file (touch), and read a file (cat).
• Understood what a "shell" is and why deleting things in the terminal has no undo, so you treat that one command with respect.

That's it. Three short lessons, about twenty-five minutes. After this,

The terminal is a text box. That's the whole secret.

If you are starting here, the terminal is a text box on your machine: type a name, press enter, the computer does it.

If you already ran a studio on this path, you already shipped a tool in the browser. This chapter is the same work on your machine: a box where you type the name of a thing you want done, press enter, and the computer does it.

If the word "terminal" still means green text and a hoodie, that picture is doing you a disservice. The truth is boring in the best way.

The terminal is a text box. You type the name of a thing you want done. You press enter. The computer does it and tells you what happened. That is the entire idea. There is nothing else hiding behind it.

You already drive your computer every day. You click a folder, it opens. You drag a file, it moves. The terminal is the same set of actions with the mouse swapped out for words. "Open that folder" becomes cd. "Show me what's in here" becomes ls. Same computer, same files, different steering wheel.

Why bother, if the mouse already works

Fair question. Here's the honest answer.

• Every tool in the rest of this course assumes it.

  running Python, using git. All of it happens in the terminal. This chapter is the door the other chapters walk through.

• It's faster once it's yours. Making twelve folders by hand takes twelve clicks and twelve typed names. In the terminal it's one line.

• It's repeatable. A click happens once and is gone. A typed command can be saved, shared, and run again. That's the whole reason developers and AI tools live here.

• The AI tools you're here to learn are terminal tools.

  The Claude CLI and the Codex CLI, the next two chapters, are programs you run by typing. You can't skip the room they live in.

What this chapter is not

It is not a deep dive. There are people who spend years getting good at the shell, and this chapter does not try to make you one of them. You will learn maybe eight commands. Eight is enough to get through this whole course and most of a real building job.

What you'll be able to do at the end

By the end of these three lessons you will have:

• Opened a terminal on your own machine, on purpose.
• Found out where you are in your files (pwd) and what's around you (ls).
• Moved into and out of folders (cd) using both the long way and the shortcuts.
• Made a folder (mkdir), made a file (touch), and read a file (cat).
• Understood what a "shell" is and why deleting things in the terminal has no undo, so you treat that one command with respect.

That's it. Three short lessons, about twenty-five minutes. After this,

The terminal is a text box. That's the whole secret.

If you are starting here, the terminal is a text box on your machine: type a name, press enter, the computer does it.

If you already ran a studio on this path, you already shipped a tool in the browser. This chapter is the same work on your machine: a box where you type the name of a thing you want done, press enter, and the computer does it.

If the word "terminal" still means green text and a hoodie, that picture is doing you a disservice. The truth is boring in the best way.

The terminal is a text box. You type the name of a thing you want done. You press enter. The computer does it and tells you what happened. That is the entire idea. There is nothing else hiding behind it.

You already drive your computer every day. You click a folder, it opens. You drag a file, it moves. The terminal is the same set of actions with the mouse swapped out for words. "Open that folder" becomes cd. "Show me what's in here" becomes ls. Same computer, same files, different steering wheel.

Why bother, if the mouse already works

Fair question. Here's the honest answer.

• Every tool in the rest of this course assumes it.

  running Python, using git. All of it happens in the terminal. This chapter is the door the other chapters walk through.

• It's faster once it's yours. Making twelve folders by hand takes twelve clicks and twelve typed names. In the terminal it's one line.

• It's repeatable. A click happens once and is gone. A typed command can be saved, shared, and run again. That's the whole reason developers and AI tools live here.

• The AI tools you're here to learn are terminal tools.

  The Claude CLI and the Codex CLI, the next two chapters, are programs you run by typing. You can't skip the room they live in.

What this chapter is not

It is not a deep dive. There are people who spend years getting good at the shell, and this chapter does not try to make you one of them. You will learn maybe eight commands. Eight is enough to get through this whole course and most of a real building job.

What you'll be able to do at the end

By the end of these three lessons you will have:

• Opened a terminal on your own machine, on purpose.
• Found out where you are in your files (pwd) and what's around you (ls).
• Moved into and out of folders (cd) using both the long way and the shortcuts.
• Made a folder (mkdir), made a file (touch), and read a file (cat).
• Understood what a "shell" is and why deleting things in the terminal has no undo, so you treat that one command with respect.

That's it. Three short lessons, about twenty-five minutes. After this,

The terminal is a text box. That's the whole secret.

If you are starting here, the terminal is a text box on your machine: type a name, press enter, the computer does it.

If you already ran a studio on this path, you already shipped a tool in the browser. This chapter is the same work on your machine: a box where you type the name of a thing you want done, press enter, and the computer does it.

If the word "terminal" still means green text and a hoodie, that picture is doing you a disservice. The truth is boring in the best way.

The terminal is a text box. You type the name of a thing you want done. You press enter. The computer does it and tells you what happened. That is the entire idea. There is nothing else hiding behind it.

You already drive your computer every day. You click a folder, it opens. You drag a file, it moves. The terminal is the same set of actions with the mouse swapped out for words. "Open that folder" becomes cd. "Show me what's in here" becomes ls. Same computer, same files, different steering wheel.

Why bother, if the mouse already works

Fair question. Here's the honest answer.

• Every tool in the rest of this course assumes it.

  running Python, using git. All of it happens in the terminal. This chapter is the door the other chapters walk through.

• It's faster once it's yours. Making twelve folders by hand takes twelve clicks and twelve typed names. In the terminal it's one line.

• It's repeatable. A click happens once and is gone. A typed command can be saved, shared, and run again. That's the whole reason developers and AI tools live here.

• The AI tools you're here to learn are terminal tools.

  The Claude CLI and the Codex CLI, the next two chapters, are programs you run by typing. You can't skip the room they live in.

What this chapter is not

It is not a deep dive. There are people who spend years getting good at the shell, and this chapter does not try to make you one of them. You will learn maybe eight commands. Eight is enough to get through this whole course and most of a real building job.

What you'll be able to do at the end

By the end of these three lessons you will have:

• Opened a terminal on your own machine, on purpose.
• Found out where you are in your files (pwd) and what's around you (ls).
• Moved into and out of folders (cd) using both the long way and the shortcuts.
• Made a folder (mkdir), made a file (touch), and read a file (cat).
• Understood what a "shell" is and why deleting things in the terminal has no undo, so you treat that one command with respect.

That's it. Three short lessons, about twenty-five minutes. After this,

The terminal is a text box. That's the whole secret.

If you are starting here, the terminal is a text box on your machine: type a name, press enter, the computer does it.

If you already ran a studio on this path, you already shipped a tool in the browser. This chapter is the same work on your machine: a box where you type the name of a thing you want done, press enter, and the computer does it.

If the word "terminal" still means green text and a hoodie, that picture is doing you a disservice. The truth is boring in the best way.

The terminal is a text box. You type the name of a thing you want done. You press enter. The computer does it and tells you what happened. That is the entire idea. There is nothing else hiding behind it.

You already drive your computer every day. You click a folder, it opens. You drag a file, it moves. The terminal is the same set of actions with the mouse swapped out for words. "Open that folder" becomes cd. "Show me what's in here" becomes ls. Same computer, same files, different steering wheel.

Why bother, if the mouse already works

Fair question. Here's the honest answer.

• Every tool in the rest of this course assumes it.

  running Python, using git. All of it happens in the terminal. This chapter is the door the other chapters walk through.

• It's faster once it's yours. Making twelve folders by hand takes twelve clicks and twelve typed names. In the terminal it's one line.

• It's repeatable. A click happens once and is gone. A typed command can be saved, shared, and run again. That's the whole reason developers and AI tools live here.

• The AI tools you're here to learn are terminal tools.

  Your next chapter is delivery studio. The same terminal skills still apply when a later tool needs them.

What this chapter is not

It is not a deep dive. There are people who spend years getting good at the shell, and this chapter does not try to make you one of them. You will learn maybe eight commands. Eight is enough to get through this whole course and most of a real building job.

What you'll be able to do at the end

By the end of these three lessons you will have:

• Opened a terminal on your own machine, on purpose.
• Found out where you are in your files (pwd) and what's around you (ls).
• Moved into and out of folders (cd) using both the long way and the shortcuts.
• Made a folder (mkdir), made a file (touch), and read a file (cat).
• Understood what a "shell" is and why deleting things in the terminal has no undo, so you treat that one command with respect.

That's it. Three short lessons, about twenty-five minutes. After this,

delivery studio has somewhere to stand.

The terminal is a text box. That's the whole secret.

If you are starting here, the terminal is a text box on your machine: type a name, press enter, the computer does it.

If you already ran a studio on this path, you already shipped a tool in the browser. This chapter is the same work on your machine: a box where you type the name of a thing you want done, press enter, and the computer does it.

If the word "terminal" still means green text and a hoodie, that picture is doing you a disservice. The truth is boring in the best way.

The terminal is a text box. You type the name of a thing you want done. You press enter. The computer does it and tells you what happened. That is the entire idea. There is nothing else hiding behind it.

You already drive your computer every day. You click a folder, it opens. You drag a file, it moves. The terminal is the same set of actions with the mouse swapped out for words. "Open that folder" becomes cd. "Show me what's in here" becomes ls. Same computer, same files, different steering wheel.

Why bother, if the mouse already works

Fair question. Here's the honest answer.

• Every tool in the rest of this course assumes it.

  running Python, using git. All of it happens in the terminal. This chapter is the door the other chapters walk through.

• It's faster once it's yours. Making twelve folders by hand takes twelve clicks and twelve typed names. In the terminal it's one line.

• It's repeatable. A click happens once and is gone. A typed command can be saved, shared, and run again. That's the whole reason developers and AI tools live here.

• The AI tools you're here to learn are terminal tools.

  The Claude CLI and the Codex CLI, the next two chapters, are programs you run by typing. You can't skip the room they live in.

What this chapter is not

It is not a deep dive. There are people who spend years getting good at the shell, and this chapter does not try to make you one of them. You will learn maybe eight commands. Eight is enough to get through this whole course and most of a real building job.

What you'll be able to do at the end

By the end of these three lessons you will have:

• Opened a terminal on your own machine, on purpose.
• Found out where you are in your files (pwd) and what's around you (ls).
• Moved into and out of folders (cd) using both the long way and the shortcuts.
• Made a folder (mkdir), made a file (touch), and read a file (cat).
• Understood what a "shell" is and why deleting things in the terminal has no undo, so you treat that one command with respect.

That's it. Three short lessons, about twenty-five minutes. After this,

The terminal is a text box. That's the whole secret.

If you are starting here, the terminal is a text box on your machine: type a name, press enter, the computer does it.

If you already ran a studio on this path, you already shipped a tool in the browser. This chapter is the same work on your machine: a box where you type the name of a thing you want done, press enter, and the computer does it.

If the word "terminal" still means green text and a hoodie, that picture is doing you a disservice. The truth is boring in the best way.

The terminal is a text box. You type the name of a thing you want done. You press enter. The computer does it and tells you what happened. That is the entire idea. There is nothing else hiding behind it.

You already drive your computer every day. You click a folder, it opens. You drag a file, it moves. The terminal is the same set of actions with the mouse swapped out for words. "Open that folder" becomes cd. "Show me what's in here" becomes ls. Same computer, same files, different steering wheel.

Why bother, if the mouse already works

Fair question. Here's the honest answer.

• Every tool in the rest of this course assumes it. Installing the Claude CLI, running Python, using git. All of it happens in the terminal. This chapter is the door the other chapters walk through.
• It's faster once it's yours. Making twelve folders by hand takes twelve clicks and twelve typed names. In the terminal it's one line.
• It's repeatable. A click happens once and is gone. A typed command can be saved, shared, and run again. That's the whole reason developers and AI tools live here.
• The AI tools you're here to learn are terminal tools. The Claude CLI, the next chapter, is a program you run by typing. You can't skip the room it lives in.

What this chapter is not

It is not a deep dive. There are people who spend years getting good at the shell, and this chapter does not try to make you one of them. You will learn maybe eight commands. Eight is enough to get through this whole course and most of a real building job.

What you'll be able to do at the end

By the end of these three lessons you will have:

• Opened a terminal on your own machine, on purpose.
• Found out where you are in your files (pwd) and what's around you (ls).
• Moved into and out of folders (cd) using both the long way and the shortcuts.
• Made a folder (mkdir), made a file (touch), and read a file (cat).
• Understood what a "shell" is and why deleting things in the terminal has no undo, so you treat that one command with respect.

That's it. Three short lessons, about twenty-five minutes. After this, the Claude CLI chapter has somewhere to stand.

The terminal is a text box. That's the whole secret.

If you are starting here, the terminal is a text box on your machine: type a name, press enter, the computer does it.

If you already ran a studio on this path, you already shipped a tool in the browser. This chapter is the same work on your machine: a box where you type the name of a thing you want done, press enter, and the computer does it.

If the word "terminal" still means green text and a hoodie, that picture is doing you a disservice. The truth is boring in the best way.

The terminal is a text box. You type the name of a thing you want done. You press enter. The computer does it and tells you what happened. That is the entire idea. There is nothing else hiding behind it.

You already drive your computer every day. You click a folder, it opens. You drag a file, it moves. The terminal is the same set of actions with the mouse swapped out for words. "Open that folder" becomes cd. "Show me what's in here" becomes ls. Same computer, same files, different steering wheel.

Why bother, if the mouse already works

Fair question. Here's the honest answer.

• Every tool in the rest of this course assumes it.

  running Python, using git. All of it happens in the terminal. This chapter is the door the other chapters walk through.

• It's faster once it's yours. Making twelve folders by hand takes twelve clicks and twelve typed names. In the terminal it's one line.

• It's repeatable. A click happens once and is gone. A typed command can be saved, shared, and run again. That's the whole reason developers and AI tools live here.

• The AI tools you're here to learn are terminal tools.

  The Claude CLI and the Codex CLI, the next two chapters, are programs you run by typing. You can't skip the room they live in.

What this chapter is not

It is not a deep dive. There are people who spend years getting good at the shell, and this chapter does not try to make you one of them. You will learn maybe eight commands. Eight is enough to get through this whole course and most of a real building job.

What you'll be able to do at the end

By the end of these three lessons you will have:

• Opened a terminal on your own machine, on purpose.
• Found out where you are in your files (pwd) and what's around you (ls).
• Moved into and out of folders (cd) using both the long way and the shortcuts.
• Made a folder (mkdir), made a file (touch), and read a file (cat).
• Understood what a "shell" is and why deleting things in the terminal has no undo, so you treat that one command with respect.

That's it. Three short lessons, about twenty-five minutes. After this,