1.2 Installation and Setup

Course: Claude Code - Essentials Section: Getting Started Video Length: 2-5 minutes Presenter: Daniel Treasure

Opening Hook

Now that you know what Claude Code can do, let's get it installed. We'll cover three methods—you pick the one that works for your setup. Most developers use native install, but we'll show all three so you can choose.

Key Talking Points

1. Why These Three Methods? (The Context)

Native Install (Recommended): Auto-updates, works everywhere, easiest for most
Homebrew: Best if you already use brew on macOS
npm/Node: Best if you're in a Node.js workflow or want a project-scoped install

What to say: "Native install is our recommended path because it auto-updates in the background. But if you're a brew person or running npm everywhere, we've got you covered."

What to show on screen: Quick text showing the three methods side by side. Don't need visuals yet—just context.

2. Native Install - macOS/Linux/WSL (The Mainstream)

Key points: - Single command, fully automated - Auto-updates in background - Works on macOS, Linux, and Windows Subsystem for Linux (WSL) - No additional dependencies

What to say: "This is the official Anthropic installation path. One command, and you're done. It handles everything—downloads, configuration, PATH setup."

What to show on screen: Type the command in a clean terminal, show the output as it installs. Highlight the "Installation complete" or success message.

3. Native Install - Windows PowerShell (The Microsoft Approach)

Key points: - Different command for PowerShell (uses irm and iex instead of curl) - Same auto-update behavior - Works on modern Windows systems

What to say: "Windows users, don't feel left out. PowerShell has its own one-liner. The install process is identical—just a different syntax."

What to show on screen: Type the PowerShell command in a PowerShell window. Show it working. You can skip actually running this if time is tight—showing the command is enough.

4. Homebrew on macOS (The Alternate)

Key points: - Uses brew install --cask claude-code (note: it's a cask, not a formula) - Requires manual updates: brew upgrade claude-code - Good if brew is your package manager

What to say: "If you manage your dev tools through Homebrew, here's your path. The tradeoff is you have to manually upgrade—brew doesn't auto-update casks."

What to show on screen: Type the brew install command. Show the output. Highlight that upgrades are manual.

5. Verification After Install (The Sanity Check)

Key points: - Run claude --version to verify installation worked - First run of claude may ask for login

What to say: "After installation, verify it worked by running claude --version. You should see a version number. If that works, you're ready for the next video."

What to show on screen: Type claude --version and show output like "Claude Code 1.0.0" or similar.

Demo Plan

Timeline: 2-3 minutes total

Show clean terminal window (fresh shell, no clutter)
Explain the three methods (30 seconds of talking points, no demo)
Demo Native Install (actual install, if feasible in recording):
Open terminal
Type the install command (macOS/Linux version)
Let it run to completion (may be 20-30 seconds)
Show success message
Verify Installation:
Run claude --version
Show version output
Mention alternatives but don't demo them (time constraint)

Alternative if live install is risky: Record the install once beforehand, then show the recording or screenshot.

Code Examples & Commands

Native Install (macOS, Linux, WSL):

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

Native Install (Windows PowerShell):

irm https://claude.ai/install.ps1 | iex

Native Install (Windows CMD):

curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

Homebrew (macOS):

brew install --cask claude-code

WinGet (Windows):

winget install Anthropic.ClaudeCode

Verify Installation:

claude --version

First Login:

cd /path/to/your/project
claude
# Follow prompts to log in

Gotchas & Tips

Auto-updates only with native install: If you use Homebrew or WinGet, set a reminder to update periodically (brew upgrade claude-code)
WSL users: Use the Linux native install, not Windows PowerShell
Login requirement: First run will ask you to authenticate—have your Claude account ready
No special permissions needed: Claude installs to your user home directory, not system-wide
PATH setup is automatic: Don't manually add Claude to PATH; the installer handles it

Lead-out

"You're installed and ready. In the next video, we'll start Claude Code for the first time and have your first conversation with it. You'll ask it questions about a sample project, and you'll see it in action."

Reference URLs

Prep Reading

Official installation documentation (verify all URLs and commands are current)
Homebrew documentation if demo'ing brew installation
Windows PowerShell basics if showing Windows install (know the difference between irm and curl)

Notes for Daniel: This is procedural, so be clear and deliberate. Speak to each method like you're helping a friend install software. If the live installation takes too long or fails, have a backup screenshot or pre-recorded version ready. The goal is confidence, not perfection.

Quick Reference