The first time I sat at a real terminal, I hated it.

Black screen. Blinking cursor. No buttons. No obvious undo. The feeling of typing a command and not being completely sure what would happen next.

It felt like flying a plane with the lights off.

But the terminal is not a hacker cave. It is not a test of whether you are “technical enough.” It is just a direct way to stand inside your own computer and tell it what to do.

For an AI-native founder, that matters because Claude Code does not work in vibes. It works in folders. It reads files. It writes files. It needs a clean local place to operate.

So in this lesson, we are not going to learn every terminal command. We are going to learn five commands and create one local workspace.

By the end, your terminal, Finder, and Zed will all point at the same folder:

~/Projects/founder-os

That folder is your first AI workshop.

In the next lesson, we will bring Claude Code into that workshop and ask it to build the first structure for us.

The leverage

Most beginner terminal tutorials teach commands like a vocabulary quiz.

That is not what we are doing.

You are learning the minimum terminal fluency required to create a local workspace, open it visually, and understand where your AI operator will work next.

That gives you three forms of leverage:

1. Orientation — you know where you are on your machine.
2. Ownership — your work lives in a local folder you control.
3. Trust — when Claude Code starts making files, you know where to look.

Simple files in clear folders are one of the strongest substrates we have for AI agents. Before you ask an agent to build, research, summarize, or organize, you need a place for that work to land.

Today we create that place.

Two ideas only

You only need two ideas for this lesson.

1. A directory is a room

A directory is a folder. A folder is a room.

When you use the terminal, you are always standing in one room on your computer. Every command runs from wherever you are standing.

If you feel lost, do not panic. Ask the terminal where you are.

2. The terminal shows you where you are

Finder is visual. Zed is editorial. The terminal is literal.

Finder lets you click through folders. Zed lets you read and edit files. The terminal tells you exactly where you are standing and lets you create or open folders directly.

The goal is not to replace Finder or Zed. The goal is to connect all three.

Terminal. Finder. Zed.

Three views into the same room.

The five commands

Open Ghostty.

We are going to use five commands.

pwd — where am I standing?

pwd

pwd means “print working directory.”

It shows the folder you are currently standing in.

You will probably see something like:

/Users/yourname

That is your home folder.

Any time you feel disoriented in the terminal, run:

pwd

Do not guess. Orient.

ls — what is in this room?

ls

ls lists what is inside the folder you are standing in.

If pwd tells you where you are, ls tells you what is around you.

Run them together:

pwd
ls

That is the basic orientation loop:

• Where am I?
• What is here?

cd — walk into another room

cd means “change directory.”

It lets you walk into another folder.

We will use it in a minute to walk into your Projects folder.

For now, just understand the pattern:

cd folder-name

You are telling the terminal: move me into this folder.

mkdir — build a new room

mkdir means “make directory.”

It creates a folder.

The pattern is:

mkdir folder-name

In a minute, you will use it to create your first Founder OS workspace.

open . — open this room in Finder

This one matters.

open .

On a Mac, open opens something visually.

The dot means “the folder I am standing in right now.”

So open . means:

Open the current folder in Finder.

This is the bridge between the terminal and the visual interface you already know.

When you run open ., Finder should open the exact folder your terminal is standing inside.

That is how you prove to your nervous system that the black screen is not magic. It is just another doorway into the same place.

Build your Founder OS workspace

Now we are going to create the folder Claude Code will use in the next lesson.

Copy and run these commands one line at a time.

mkdir -p ~/Projects
cd ~/Projects
mkdir founder-os
cd founder-os
open .
open -a Zed .

Now slow down. Here is what each line did.

mkdir -p ~/Projects

mkdir -p ~/Projects

This creates a Projects folder inside your home folder.

The ~ means your home folder.

So this path:

~/Projects

means:

/Users/yourname/Projects

The -p part makes the command safe to run even if the folder already exists. If Projects is already there, nothing bad happens.

This folder becomes your home base for AI-native work.

cd ~/Projects

cd ~/Projects

This walks you into the Projects folder.

Check it:

pwd

You should see a path ending in:

/Projects

Now your terminal is standing in your Projects room.

mkdir founder-os

mkdir founder-os

This creates a new folder called founder-os.

That is your first local AI-native workspace.

Do not worry about what goes inside it yet. In this lesson, we only create the room.

In the next lesson, Claude Code will help organize it.

cd founder-os

cd founder-os

This walks you into the new workspace.

Check it:

pwd

You should see a path ending in:

/Projects/founder-os

This is the most important location in the lesson.

You are now standing inside your AI workshop.

open .

open .

Finder should open.

It should show your founder-os folder.

This is the same folder your terminal is standing inside.

Terminal and Finder are now looking at the same room.

open -a Zed .

open -a Zed .

This opens the current folder in Zed.

Now Zed is also looking at the same room.

You have three views into one workspace:

• Terminal: where you command the machine.
• Finder: where you see the folder visually.
• Zed: where you will read and edit files.

This is the moment the terminal stops being a black box.

You know where you are.

If zed . fails, nothing is broken

You may see people online use this command:

zed .

If you try it and see this:

zsh: command not found: zed

nothing is broken.

It only means the optional Zed command-line shortcut is not installed in your shell yet.

For this lesson, use:

open -a Zed .

That uses macOS to open Zed directly and does not require the optional shortcut.

Later, if you want the shorter zed command, you can install Zed’s shell command from inside Zed. But you do not need it today.

Three views into one room

Pause for a second and look at what you just built.

Your terminal is standing in:

~/Projects/founder-os

Finder is showing that same folder.

Zed is open to that same folder.

That is the foundation of AI-native work.

Not prompts. Not hacks. Not a giant dashboard.

A clean local workspace that you control.

When Claude Code enters this folder in the next lesson, it will be operating inside a known room. You will know where it is. You will know where its files appear. You will be able to inspect its work in Zed and Finder.

That is how trust starts.

What we are not teaching yet

We are intentionally stopping here.

We are not learning how to write files from the terminal.

We are not learning how to move files.

We are not learning how to search files.

We are not learning how to delete files.

We are not learning pipes or command chaining.

You do not need those yet.

The win today is simpler:

1. You opened the terminal.
2. You found where you were standing.
3. You created ~/Projects/founder-os.
4. You opened that folder in Finder.
5. You opened that folder in Zed.
6. You understand that this is where Claude Code will work next.

That is enough.

What comes next

In the next lesson, we will open Claude Code inside:

~/Projects/founder-os

Then we will give Claude Code its first real job:

Bootstrap the initial Founder OS folder structure and create a CLAUDE.md file that explains how this workspace should work.

That is when the AI operator enters the workshop.

Today, you built the room.

Reflection

Answer these in two sentences each.

1. What changed when you saw your machine as rooms instead of icons?
2. What folder in your life currently feels like an unfinished relationship?
3. What is one local container you want your AI team to help you build?

Success criteria

You are done when all of this is true:

• You can open Ghostty.
• You can run pwd and understand the path it shows.
• You can run ls and understand that it lists what is in the current folder.
• You created ~/Projects/founder-os.
• Finder opens that folder when you run open ..
• Zed opens that folder when you run open -a Zed ..
• You understand that Claude Code will work from this folder in the next lesson.

That is the foundation.

Now you have a workshop.