Session Slides

I want to start with something honest. The command line looks intimidating. It is a black screen with text and no buttons. And most people see it and immediately close it. That reaction is understandable - but it is also the reason those same people hit a ceiling with AI tools. Claude Code lives behind this screen. Dispatch setup lives behind this screen. MCP connections, automation scripts, almost every powerful AI integration - all behind this screen. Today we are going to open that door together. Not to make you a developer. Just to make you someone who is not afraid of a terminal.

Here is the important reframe. The terminal is not a programming environment. It is not a place where code lives. It is a text-based version of the file manager you already know. When you double-click a folder on your desktop, you are doing the same thing as typing "cd folder-name" in the terminal. When you right-click and say "create new folder," you are doing the same thing as typing "mkdir folder-name." The terminal just does these things faster, and it lets you chain them together in ways a mouse cannot. That is the only difference. The computer is doing the same work. You are just talking to it in a different language - and that language has about five words you will use 90 percent of the time.

These five commands will cover almost everything you need to do as an AI Officer who uses the terminal. PWD tells you your current location - think of it as the address bar in your file manager. LS on Mac or DIR on Windows lists everything in the folder you are currently in - same as opening a folder and seeing the files inside. CD changes your location - type "cd Documents" and you move into the Documents folder. MKDIR creates a new folder. And the fifth one is a pattern rather than a single command: when you install an AI tool, it will give you a command to run - something like "claude" or "python script.py" - and you just type it and press enter. That is the full vocabulary for today.

If you are on a Mac, open the Terminal app. You can find it by searching "Terminal" in Spotlight. If you are on Windows, open Command Prompt by searching "cmd" in the Start menu, or PowerShell by searching "PowerShell." The main differences: on Mac, the command to list files is "ls." On Windows, it is "dir." Most other commands are the same. If you are setting up Claude Code or other AI tools, they will usually tell you exactly what to type on each operating system. You do not need to memorize the differences. You just need to know which app to open.

Everyone do this right now. Open your terminal. If you are on a Mac, press Command + Space, type Terminal, press enter. If you are on Windows, press the Windows key, type cmd, press enter. You will see a black or white screen with a blinking cursor. Do not panic. Type pwd if you are on a Mac, or just cd if you are on Windows, and press enter. You will see a file path. That is where you are on your computer right now. You just had your first conversation with your operating system. That is the whole move. Everything else is just more specific versions of that. Post what you see in the chat - the file path your terminal printed. We will use it to navigate together in the next slide.

Here is why this matters for AI Officers specifically. Claude Code is installed from the terminal with one command and then run from the terminal. When you want to connect Claude to a new tool using the Model Context Protocol, you configure that connection from the terminal. When your team builds an automation script, it runs from the terminal. Every powerful AI tool has a terminal component - it is where the installation happens, where the configuration happens, and where you trigger the work. You do not need to write any of this. The AI tools give you the exact commands to type. But you do need to know how to open the terminal, navigate to the right folder, and paste in a command. That is the skill. And it takes about 20 minutes to get comfortable with it.

Here is your challenge for this week. Open your terminal. Do three things in sequence. First, navigate to your Documents folder - type "cd Documents" and press enter. If your Documents folder is somewhere else, use pwd first to figure out where you are, then cd your way there. Second, list the files in that folder with ls on Mac or dir on Windows. Third, create a new folder called ai-workspace by typing "mkdir ai-workspace" and pressing enter. Take a screenshot of your terminal showing these commands and the output. That is your submission. Along with the screenshot, write one sentence on what felt harder than you expected, and one sentence on what was easier. Your AI Buddy is not grading your technical skill - it is grading your willingness to open the door.

Here is the leadership lens. The people who get promoted fastest in AI programs are not always the ones who know the most about AI. They are the ones who can operate across the full stack - from a conversation in ChatGPT to a script in the terminal. You are not learning to code. You are learning to not be blocked. Every powerful AI tool, every deep integration, every automation system that is worth building has a terminal component somewhere in its setup. Once you are comfortable with these five commands, you can follow any setup guide, install any tool, and run any script your team needs. The door is open. Walk through it.