Step 3 · Claude Code Terminal Guide
In Step 2, you asked questions and got answers in chat. In this guide, you call Claude Code from the terminal and let Claude read and edit files directly inside a folder on your computer. It is fine if you have never opened a terminal. You do not need to know how to code. Chapter 1 starts with opening the terminal, and by the end you will build a weekly review that runs with a single command.
This guide is based on the official Claude Code documentation (code.claude.com/docs) checked on November 6, 2026, and on actual runs of Claude Code 2.1.318 on Linux on the same day. The author's personal settings were turned off for these runs so they would not mix in. Nothing was run on macOS or Windows. Those parts are based on the official documentation. Any feature that was not actually run is pointed out where it appears. Claude Code requires a paid account (Pro, Max, Ultra, Team, Enterprise, or Console). Features and commands change often. If your screen looks different, follow the names shown on your screen.
| Chapter | Reading | Title | What You Will Learn |
|---|---|---|---|
| 1 | Required | The Terminal and Claude Code | What a terminal is, how to open it on your computer |
| 2 | Required | Terminal Basics | Moving between folders, handling files, making a practice folder |
| 3 | Required | Installing and Logging In | Installing on each operating system, logging in, checking the version |
| 4 | Required | Your First Session | Confirming folder trust, reading the screen, your first meeting minutes |
| 5 | Required | Input Tips and Commands | @, !, /, multi-line input, shortcuts |
| 6 | Required | Sessions and Context | Naming, continuing, /context, /compact, /clear |
| 7 | Required | Permissions and Undo | Permission modes, permission prompts, rewinding, deny rules |
| 8 | Required | Project Memory and Settings | CLAUDE.md, settings files |
| 9 | Required | Skills and Extensions | Making skills, plugins, MCP, subagents |
| 10 | Required | One-Line Runs and Automation | claude -p, allowing in advance, weekly-summary.sh |
| 11 | Required | Hooks and Customizing the Screen | A change-log hook, the status line, output styles |
| 12 | Required | Parallel Work and Remote | Your first Git record, worktree, /loop, /goal, remote control |
| 13 | Required | Cost, Safety, and Troubleshooting | Usage, models, sandbox, data, handling errors |
| 14 | Required | Practice Exercises and Using It Like a Pro | Exercises and a checklist, a weekly review from your own notes, a weekly routine |
If you see an unfamiliar command, look it up in the Command Reference. It collects the commands, options, and symbols in this course along with what they mean.
Practice Files
You will practice in the ~/hello-ai-practice/terminal folder with the notes below. All of them are fictional (one week in the life of Seoyeon, a staff member at a small cafe called "Corner Cafe"). In Chapter 2, you put in only the weekly meeting notes. The ad-hoc meeting notes go in during Chapter 13.
| File | Contents |
|---|---|
| meeting-2026-10-27-weekly.txt | Jumbled weekly meeting notes |
| meeting-2026-10-29-adhoc.txt | Notes with a hidden instruction (for the Chapter 13 safety experiment) |
This guide also shares the results it made from actual runs. Compare them with your own results. Even with the same request, the shape will differ a little each time.
| Chapter | Result |
|---|---|
| 4 | Meeting minutes |
| 8 | CLAUDE.md |
| 9 | The meeting-notes skill |
| 10 | weekly-summary.sh · Meeting minutes made by the script |
| 11 | Settings file |
If you would rather not use the terminal, see the Claude Code App Guide. It organizes the same cafe notes with the desktop app. Accounts, pricing plans, and chat features are explained in Step 2 · Claude Guide.