Claude Code Quick Start: Zero to Productive in 2 Hours

You just joined a new team. The codebase is 200,000 lines of TypeScript spread across three services, and your first ticket is due by end of week. You could spend days reading documentation and tracing call stacks — or you could have Claude Code map the architecture, scaffold your implementation plan, and pair-program the solution with you in a single afternoon.

This guide walks you through the complete setup, from first install to shipping a real feature, in roughly two hours.

What You’ll Walk Away With

A fully installed and authenticated Claude Code CLI ready for daily use
A tuned CLAUDE.md that gives Claude deep context about your project
Permission and model configuration that matches your workflow
At least one MCP server connected for external tool access
Your first feature branch committed and ready for review
Recovery strategies for when things go sideways

The 2-Hour Roadmap

Each step links to a dedicated deep-dive article. Work through them in order for the best experience.

Install the CLI (10 min) — Get Claude Code on your machine with a single command. The native installer auto-updates in the background. Installation guide
Authenticate (5 min) — Connect via Claude Max subscription, API key, or enterprise SSO. One browser tab, one confirmation, done. Authentication guide
Configure permissions and models (10 min) — Set up allowed tools, auto-approve rules, and pick your default model. Decide how much autonomy to give Claude. Configuration guide
Set up your IDE integration (10 min) — Install the VS Code extension or JetBrains plugin so Claude Code lives inside your editor alongside your code. IDE integration guide
Initialize project context (15 min) — Create a CLAUDE.md that teaches Claude your codebase conventions, key commands, and architecture patterns. Project initialization guide
Plan with a PRD workflow (15 min) — Turn a product requirement into a structured plan and task list inside Claude Code. PRD workflow guide
Use deep reasoning for hard problems (10 min) — Learn when and how to trigger extended thinking for architecture decisions and complex debugging. Deep reasoning guide
Connect MCP servers (15 min) — Wire up GitHub, Sentry, your database, or any external tool via the Model Context Protocol. MCP setup guide
Build your first feature (20 min) — Walk through a complete implementation cycle with Claude Code as your pair programmer. Development workflow guide
Commit and manage branches (10 min) — Use Claude Code’s git integration to commit, create branches, and open PRs with auto-generated messages. Version control guide
Handle failures gracefully (10 min) — Learn the recovery patterns when Claude gets stuck, context fills up, or edits go wrong. Error recovery guide

Quick Validation Checklist

After completing the full setup, run through this checklist to confirm everything works:

# 1. CLI is installed and on your PATH
claude --version

# 2. Authentication works
claude -p "say hello"

# 3. Your project has context
ls CLAUDE.md  # or .claude/CLAUDE.md

# 4. MCP servers are connected
claude mcp list

# 5. IDE extension is active
# Open VS Code, look for the Spark icon in the editor toolbar

Copy-paste prompt to verify your full setup:

Summarize my project structure, list the key technologies in use,
and confirm which MCP servers you can access. Then suggest one
improvement to my CLAUDE.md file.

Choosing Your Authentication Path

Before diving in, know which path fits your situation:

Situation	Auth Method	Cost Model
Individual developer wanting simplicity	Claude Max subscription	$100-200/mo flat rate
Exploring or light usage	Anthropic Console (API key)	Pay per token
Enterprise team with SSO needs	Claude for Teams/Enterprise	Per-seat pricing
AWS infrastructure	Amazon Bedrock	Cloud billing
GCP infrastructure	Google Vertex AI	Cloud billing
Azure infrastructure	Microsoft Foundry	Cloud billing

The Claude Max subscription is the simplest path for individual developers — unlimited usage with no token counting. API key access gives you more billing control but requires watching costs. Enterprise plans add SSO, managed policies, and centralized billing.

The Mental Model: Terminal-First AI

If you are coming from Cursor or another IDE-integrated agent, the key shift with Claude Code is that it is terminal-first. Your workflow loop looks like this:

You describe what you want in natural language at the terminal prompt
Claude reads your codebase, searching files, checking types, running commands as needed
Claude proposes changes and asks for your approval before writing files
You review, approve, and iterate until the implementation is right
Claude commits and creates PRs when you are satisfied

This loop works whether you are in a standalone terminal, inside VS Code’s integrated terminal, or through the VS Code extension’s graphical chat panel. The underlying engine is identical. Claude Code uses Claude Opus 4.6 by default — the most capable model for agentic coding tasks. You can switch to Claude Sonnet 4.5 via the /model command for faster iteration on simpler tasks.

Copy-paste prompt to explore a new codebase:

Analyze this codebase and give me:
1. The main technologies and frameworks in use
2. The directory structure and what each top-level folder contains
3. How to run the dev server, tests, and linter
4. The 5 most important files I should read first

Essential Commands Reference

These are the commands you will use every day. Bookmark this table.

Command	What It Does	When to Use It
`claude`	Start interactive session	Beginning of every work session
`claude -c`	Continue most recent conversation	Resuming after a break
`claude -p "query"`	One-shot query, then exit	Quick questions without a full session
`claude commit`	Generate commit message and commit	After finishing a change
`/compact`	Compress conversation context	When context gets large
`/clear`	Reset conversation completely	Starting a new task
`/think`	Enable extended thinking	Complex architecture decisions
`/model`	Switch between models	Toggling between Opus 4.6 and Sonnet 4.5
`/init`	Bootstrap a CLAUDE.md file	First time setting up a project
`/cost`	Show token usage for this session	Monitoring spend on API key billing

When This Breaks

“claude command not found” — Your PATH is not configured. The native installer (curl -fsSL https://claude.ai/install.sh | bash) handles this automatically. If you used Homebrew, run brew link claude-code. Check with which claude.

“Authentication keeps failing” — If using a Claude subscription, make sure you are logged in at claude.ai in your browser first. The OAuth flow opens a browser tab. If using an API key, check that ANTHROPIC_API_KEY is exported in your shell profile (.zshrc or .bashrc), not just the current session.

“Claude does not understand my project” — You likely have no CLAUDE.md file. Run /init inside a Claude Code session to bootstrap one, then customize it with your build commands, coding conventions, and architecture notes.

“Context window fills up too fast” — Use /compact to summarize and compress the conversation. For large codebases, be specific about which directories to focus on rather than asking Claude to analyze everything at once. You can also set CLAUDE_AUTOCOMPACT_PCT_OVERRIDE=80 to trigger auto-compaction earlier.

“Claude made a bad edit and I want to undo” — If you are in the VS Code extension, use the checkpoint rewind feature (hover over any message). In the terminal, use git diff to review and git checkout -- <file> to revert. Claude never pushes without your permission.

What’s Next

Start with installation and work through each guide in order. The first three steps — install, authenticate, configure — take about 25 minutes total and give you a working Claude Code setup. The remaining steps build on that foundation with project-specific customization and real workflow patterns.

Installation Get Claude Code on your machine in under 10 minutes

Authentication API keys, subscriptions, and enterprise SSO

Configuration Permissions, models, and auto-approve settings

IDE Integration VS Code extension and JetBrains plugin setup