Get Up and Running in 10 Minutes

2.1 The Main Idea

The chapter's message is simple: getting started with Claude Code should not feel like a large software-installation project.

The author's first setup experience was essentially:

1. Install Claude Code
2. Type: claude
3. Press Enter
4. Type: hello
5. Claude replies

2.2 Three Ways to Install Claude Code

The book describes three main installation methods. macOS, Linux and Windows are supported, with different preferred methods depending on the operating system.

2.3 Install on macOS or Linux

Open your terminal. On macOS this could be Terminal or iTerm2. On Linux, use your preferred terminal.

curl -fsSL https://claude.ai/install.sh | bash

The installation script is described as automatically detecting the system, downloading the Claude Code binary and adding the claude command to your PATH.

After installation, launch Claude Code with:

claude

2.4 Install with Homebrew on macOS

If you already use Homebrew, the book gives this alternative:

brew install --cask claude-code

For the user, the result is the same: you should then be able to launch Claude Code with:

claude

2.5 Install on Windows

The chapter highlights one important Windows prerequisite: Git for Windows.

Step 1 — Install Git for Windows

The book says Git for Windows provides the Git Bash terminal and its Unix-style toolchain.

winget install Git.Git

You can also install Git through its normal Windows installer.

Step 2 — Install Claude Code

Open PowerShell or Git Bash and run:

winget install Anthropic.ClaudeCode

Step 3 — Verify

Open a new terminal window and run:

claude -version

If a version number appears, the installation is working.

2.6 Choosing Your Working Environment

You do not have to use Claude Code only in the terminal. The book describes several environments.

2.7 Why Learn the Terminal First?

If you are used to VS Code, the terminal may initially feel unfamiliar. But the book wants you to understand the terminal-native workflow first because it gives you a clear picture of what Claude Code is.

Terminal
   ↓
Claude Code
   ↓
Files + Shell + Git + Tools
   ↓
Project

Once you understand this foundation, using Claude Code through an IDE becomes easier because the extension is still working with the underlying CLI.

2.8 Accounts and Pricing

Claude Code requires an Anthropic account. When you launch it for the first time, the browser can open automatically so you can log in or sign up.

The book's April 2026 edition lists these paid plans:

How should a beginner choose?

The book suggests a simple approach:

Start with Pro
     ↓
Use Claude Code for a few days
     ↓
Observe your usage
     ↓
If limits become a real problem
     ↓
Consider a higher plan

The book also describes Anthropic API/token-based billing as an option for enterprise users who need custom integrations or compliance-related workflows.

2.9 Your First Conversation

Now comes the important part: actually talking to Claude Code.

Step 1 — Create a test project

Claude Code uses your current directory as its working directory. So it is useful to start inside a dedicated folder.

mkdir ~/my-first-project
cd ~/my-first-project

Step 2 — Launch Claude Code

claude

On first launch, the book says a browser window will open for Anthropic login. After authentication, the terminal displays the interactive Claude Code interface.

Step 3 — Give your first instruction

Try a very simple request:

Create a simple HTML page that displays
"Hello, Claude Code!" with some nice CSS styling.

Claude Code should work inside the current directory and create the HTML file.

Step 4 — Open the result

Use the appropriate command for your operating system:

# macOS
open index.html

# Linux
xdg-open index.html

# Windows
start index.html

2.10 The First Claude Code Loop

This tiny example introduces the basic workflow that the rest of the book builds on.

This is important because you do not need to perfectly describe the final result in your first message. You can improve the result through conversation.

Example: first request

Build me a personal homepage.
Single-page HTML, make it look good.

Then improve it

Change the color scheme.
Use a dark background with light text.
Switch to a serif font.

Add an animated gradient background effect.

The book emphasizes that this repeated cycle is the foundation of conversational programming.

2.11 VS Code Integration

If you want to use Claude Code inside VS Code, the book describes this process:

1. Open the VS Code Extensions marketplace.
2. Search for Claude Code.
3. Install the official Anthropic extension.
4. Open the Claude Code icon in the sidebar.

The important concept is that the extension uses the same underlying CLI, so the login state is shared.

2.12 Desktop App

The book also describes a standalone desktop application for users who prefer not to work directly in the terminal.

The important idea is that the desktop app provides a graphical way to access the same underlying Claude Code capability.

2.13 Verification Checklist

Before moving to the next chapter, the book recommends checking several capabilities.

2.14 Troubleshooting

Problem 1 — Cannot connect or log in

The book suggests checking whether your machine can reach Anthropic's API servers.

curl -I https://api.anthropic.com

If you receive an HTTP status code, the network is reachable. If the command times out, the problem may be related to your network environment.

Problem 2 — Permission denied during installation

On macOS or Linux, the book says not to immediately reach for sudo. Instead, make sure your local binary directory exists and is writable:

mkdir -p ~/.local/bin

curl -fsSL https://claude.ai/install.sh | bash

If necessary, check whether ~/.local/bin is included in your PATH.

Problem 3 — Windows problems

Make sure Git for Windows is installed and use Git Bash when appropriate. The book specifically warns that ordinary CMD can cause issues because Claude Code depends on the Unix toolchain supplied by Git Bash.

2.15 Updating Claude Code

The chapter explains that Claude Code updates rapidly and that updates can contain meaningful capability improvements, not just bug fixes.

Native Install

curl -fsSL https://claude.ai/install.sh | bash

Homebrew

brew upgrade --cask claude-code

Windows / WinGet

winget upgrade Anthropic.ClaudeCode

2.16 Installation → First Project Mental Model

Your Computer
     │
     ├── Terminal
     │      │
     │      └── claude
     │             │
     │             ├── Read project
     │             ├── Create/edit files
     │             ├── Run commands
     │             └── Work with tools
     │
     └── Your Project
            ├── index.html
            ├── source files
            └── other project files

The key concept is that Claude Code operates relative to the directory in which you launch it.

2.17 Common Beginner Mistakes

• Installing the IDE extension first: the book recommends getting the CLI working first.
• Running Claude from the wrong directory: remember that the current directory is its working directory.
• Using ordinary CMD on Windows: use the Git Bash environment described by the book.
• Using sudo immediately: first investigate local permissions and PATH.
• Trying to build a huge project immediately: first prove that installation and the basic loop work.
• Expecting the first generated result to be perfect: conversational programming is iterative.
• Memorizing commands without understanding the workflow: first learn install → launch → ask → review.

2.18 Interview / Revision Questions

1. What is the main purpose of this chapter?
2. What are the three installation methods described by the book?
3. Which installation method is recommended for macOS/Linux beginners?
4. What prerequisite does Windows need before Claude Code installation?
5. Why does the book warn about using CMD on Windows?
6. What is PATH and why is it relevant to Claude Code installation?
7. What environments can Claude Code be used in?
8. Why does the book recommend learning the terminal CLI first?
9. What happens the first time you run claude?
10. Why should you launch Claude Code from a project directory?
11. What is the purpose of the first HTML test?
12. What is the basic conversational programming loop?
13. How can you verify that Claude Code is correctly installed?
14. What should you check if Claude cannot connect?
15. How can Claude Code be updated?

2.19 Practice Exercises

Who are you? What can you help me with?

What does this project do?

2.20 Quick Memory Map

Get Started
│
├── Install
│   ├── Native → macOS/Linux
│   ├── Homebrew → macOS
│   └── WinGet → Windows
│
├── Choose Environment
│   ├── Terminal CLI
│   ├── VS Code
│   ├── Desktop
│   ├── Web
│   └── JetBrains
│
├── Login
│   └── Anthropic account
│
├── Start
│   └── claude
│
├── Test
│   ├── Create file
│   ├── Read project
│   └── Run command
│
└── Core Loop
    Say → Build → See → Improve

2.21 Final Takeaway

This teaching edition is based on Chapter 2, “Get Up and Running in 10 Minutes,” from the supplied April 2026 edition of Claude Code: The Complete Guide. Installation commands, plan names, prices and product interfaces can change over time, so use the source edition as the learning reference and verify current product details before installation or purchase.