Getting Started with Claude Code

How to use Claude Code from install to your first question and first change, following the official steps, run locally, with the snags we hit along the way.

Claude Code is an AI coding agent that runs in your terminal. This walks from install to a first question and a first small change, in the order of the official docs. We ran what we could locally (install, --version, --help, claude doctor); we did not log in or call the model (2026-10-16). Plans and prices are in What Claude Code Really Costs; how it differs from other tools is in Choosing a Coding Agent.

Before you start

The setup page lists (https://code.claude.com/docs/en/setup, checked 2026-10-16): macOS 13.0+, Windows 10 1809+ or Windows Server 2019+, Ubuntu 20.04+, Debian 10+, Alpine Linux 3.19+; 4 GB+ RAM, x64 or ARM64; an internet connection; Bash, Zsh, PowerShell or CMD. It also requires a Pro, Max, Team, Enterprise or Console account; as of October 16, 2026, the free claude.ai plan doesn’t include Claude Code.

Install

The native installer comes first. The commands below are copied from the official docs; we did not run the native installer or the Windows commands locally.

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

Windows has separate commands (same source):

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

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

Homebrew (brew install --cask claude-code) and WinGet (winget install Anthropic.ClaudeCode) also work. Native installs auto-update in the background; Homebrew and WinGet don’t, so run brew upgrade or winget upgrade yourself.

With npm, the package is @anthropic-ai/claude-code and needs Node.js 22+; on older Node, npm prints an EBADENGINE warning rather than failing (same source). We installed it with npm into an empty temp HOME on Node.js v20.19.2:

npm WARN EBADENGINE }
added 3 packages in 5s
2.1.301 (Claude Code)

As documented: a warning, but it installed and ran. For daily use, upgrade Node or use the native installer.

Check the install

Open a new terminal and run claude --version. For more, claude doctor prints read-only install and settings diagnostics without starting a session (same source). Without logging in, ours showed:

Running: npm-global (2.1.301)
Platform: linux-x64
Auto-updates: enabled
1 warning found
- Can't auto-update: npm global folder isn't writable
  Fix: Run claude install to switch to the native installer (no sudo) ...

If claude isn’t found, it’s usually not on your shell’s PATH: see Claude Code Env Vars Not Working.

First session

Run claude in your project directory. On first use you log in through the browser with a subscription or Console account (https://code.claude.com/docs/en/quickstart, checked 2026-10-16). Start with read-only questions, as the quickstart suggests: “what does this project do?”, “where is the main entry point?”, “explain the folder structure.” Claude Code reads files as needed.

First change

Then ask for something small, like the quickstart’s “add a hello world function to the main file.” Claude shows the change; approve it after reading. The permission mode decides what runs without asking; Shift+Tab switches it (same source). Early on, keep approvals on and read every diff.

Handy commands

Our claude --help lists -c, --continue, -r, --resume and -p, --print. /init drafts a CLAUDE.md (https://code.claude.com/docs/en/commands, checked 2026-10-16); what to keep in it is in Trim Your CLAUDE.md.

Summary

• Check requirements and that you have a paid plan or Console account.
• Native installs auto-update; Homebrew and WinGet don’t.
• npm needs Node.js 22+; run claude doctor after installing.
• Start with read-only questions; ask for small changes and read diffs.
• Prices: the pricing article. Other tools: the comparison article.