Skip to content

This page was translated from the Korean original with AI and may contain errors.

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.

ChapterReadingTitleWhat You Will Learn
1RequiredThe Terminal and Claude CodeWhat a terminal is, how to open it on your computer
2RequiredTerminal BasicsMoving between folders, handling files, making a practice folder
3RequiredInstalling and Logging InInstalling on each operating system, logging in, checking the version
4RequiredYour First SessionConfirming folder trust, reading the screen, your first meeting minutes
5RequiredInput Tips and Commands@, !, /, multi-line input, shortcuts
6RequiredSessions and ContextNaming, continuing, /context, /compact, /clear
7RequiredPermissions and UndoPermission modes, permission prompts, rewinding, deny rules
8RequiredProject Memory and SettingsCLAUDE.md, settings files
9RequiredSkills and ExtensionsMaking skills, plugins, MCP, subagents
10RequiredOne-Line Runs and Automationclaude -p, allowing in advance, weekly-summary.sh
11RequiredHooks and Customizing the ScreenA change-log hook, the status line, output styles
12RequiredParallel Work and RemoteYour first Git record, worktree, /loop, /goal, remote control
13RequiredCost, Safety, and TroubleshootingUsage, models, sandbox, data, handling errors
14RequiredPractice Exercises and Using It Like a ProExercises 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.

FileContents
meeting-2026-10-27-weekly.txtJumbled weekly meeting notes
meeting-2026-10-29-adhoc.txtNotes 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.

ChapterResult
4Meeting minutes
8CLAUDE.md
9The meeting-notes skill
10weekly-summary.sh · Meeting minutes made by the script
11Settings 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.