How do I install Claude Code on Mac?

Run curl -fsSL https://claude.ai/install.sh | bash in your terminal. This is the recommended method as it auto-updates. Alternatively use Homebrew: brew install --cask claude-code (manual updates required).

How do I install Claude Code on Windows?

First install Git for Windows, then run irm https://claude.ai/install.ps1 | iex in PowerShell. You can also use WinGet: winget install Anthropic.ClaudeCode. The PowerShell method auto-updates while WinGet does not.

Can I use Claude Code in VS Code?

Yes. Search for Claude Code in the VS Code Extensions panel (Cmd+Shift+X) and install the Anthropic extension. It provides inline diffs, @-mentions, plan review, and conversation history. The same extension also works in Cursor.

Is Claude Code free to install?

Claude Code is free to install but requires a Claude account to use. The free tier has limited usage. Most daily users need the Pro ($20/month) or Max ($100 to $200/month) plan for meaningful work.

What is a CLAUDE.md file and do I need one?

CLAUDE.md is a markdown file in your project root that Claude Code reads at the start of every session. It contains your project context, coding conventions, and instructions. You do not need one to start, but it dramatically improves Claude Code output by giving it informed context about your project.

How to install Claude Code in under 3 minutes (Mac, Windows, VS Code, CLI)

March 26, 2026 — By Rahul Lalia

TL;DR: Three minutes to install. A lifetime of how did I ever code without this.

I started using Claude Code inside VS Code. The extension, the sidebar, the inline diffs. It was nice. Comfortable. Familiar.

That lasted about two weeks.

Then I switched to running Claude Code directly in Ghostty, a GPU-accelerated terminal built by Mitchell Hashimoto (the creator of Terraform and Vagrant). Split panes with Cmd+D, zero config out of the box, hundreds of themes that auto-switch between light and dark mode. The same terminal that the developers working on Claude Code itself use.

I haven't opened the VS Code extension since.

But here's the thing. Whether you use VS Code, the terminal, the Desktop app, or JetBrains, the actual install takes less than 3 minutes. Most of that time is just waiting for the download. The part that makes Claude Code useful? That's the setup after the install. And that's where most guides stop too early.

Here's the full walkthrough. Install, setup, and the first thing you should do before writing a single prompt.

Install Claude Code on Mac (the one-liner)

Open your terminal and run this:

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

That's it. The native installer downloads the binary, adds it to your PATH, and sets up auto-updates so you're always on the latest version.

If you prefer Homebrew:

brew install --cask claude-code

One difference. Homebrew installs don't auto-update. You'll need to run brew upgrade claude-code manually to get new features and security fixes. The native install handles that for you.

After the install finishes, navigate to any project folder and type:

cd your-project
claude

First time you run it, Claude Code prompts you to log in with your Claude account. Sign in, and you're live.

![Hand-drawn terminal window sketch showing a curl install command with a checkmark and done, arrow pointing to 3 minutes](One command. Three minutes. You are running.)

Install Claude Code on Windows

Windows needs one prerequisite: Git for Windows. Install that first if you don't have it.

Then open PowerShell and run:

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

Or if you prefer Windows CMD:

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

WinGet works too:

winget install Anthropic.ClaudeCode

Same deal as Homebrew. WinGet installs don't auto-update. The native PowerShell install does.

Install Claude Code in VS Code (the visual route)

This is the easiest entry point if you've never used a terminal tool before.

Open VS Code. Hit Cmd+Shift+X (Mac) or Ctrl+Shift+X (Windows/Linux) to open the Extensions panel. Search for "Claude Code" and install the one by Anthropic.

After installing, open the Command Palette (Cmd+Shift+P or Ctrl+Shift+P), type "Claude Code", and select Open in New Tab.

You get inline diffs, @-mentions to reference files, plan review, and conversation history right inside your editor. It's a good way to start.

The same extension works in Cursor too. Just search "Claude Code" in the Cursor extensions panel.

And you know what? I'd recommend starting here if you're new to Claude Code. Get comfortable with what it can do. See the diffs, watch it edit files, get a feel for the workflow. Then when you're ready for more speed and control, move to the terminal.

Install Claude Code in JetBrains (IntelliJ, PyCharm, WebStorm)

Install the Claude Code plugin from the JetBrains Marketplace and restart your IDE. That's the whole process.

It gives you interactive diff viewing and selection context sharing. Not as full-featured as VS Code or the terminal, but it works if JetBrains is your home.

Why I use the terminal (and why you might want to, eventually)

VS Code is comfortable. The terminal is powerful.

In the terminal, Claude Code runs with zero UI overhead. No sidebar competing for screen space. No extension loading. Just you, the prompt, and your codebase.

But the real reason I switched? Ghostty.

Cmd+D splits your terminal horizontally. Cmd+Shift+D splits vertically. So I'll have Claude Code running in one pane, my project files in another, and a test runner in a third. All in one window.

Ghostty 1.3.0 (released March 9, 2026) added scrollback search, native scrollbars, and click-to-move-cursor in shell prompts. It also lets you control working directory inheritance for new tabs and splits independently, which matters when you're jumping between client projects.

It's platform-native, not Electron. GPU-accelerated rendering. Starts instantly. And the developers building Claude Code use it themselves, which tells you something about how well these two tools play together.

![Hand-drawn bar chart on graph paper comparing VS Code labeled comfortable with a short bar versus Terminal labeled powerful with a tall bar](Most people start in VS Code. The ones who stay move to the terminal.)

If you want to try the terminal route, install Ghostty from ghostty.org, then install Claude Code with the curl command above. Open Ghostty, cd into your project, type claude, and you're running.

The first thing to do after installing (most guides skip this)

You've installed Claude Code. You've typed claude in a project folder. Now what?

Before you ask it to build anything, do this:

Create a file called CLAUDE.md in your project root. This is the instruction file Claude Code reads at the start of every session. It tells Claude about your project: what tech stack you use, what conventions to follow, where things live, what to avoid.

Here's a minimal starting point:

# Project: [your project name]

## Tech stack
- [framework, language, database]

## Rules
- [coding conventions you care about]
- [files or folders to never modify]

## Context
- [what this project does in 2 sentences]

Even something that basic makes a huge difference. Without a CLAUDE.md, Claude Code works blind. With one, it works informed.

I wrote a full deep dive on this: The CLAUDE.md trick that serious teams are using to 10x their AI output.

At RSL/A, Rahul Lalia here, every single client project has its own CLAUDE.md. Some of them are 500+ lines long. They include naming conventions, API keys location, deployment instructions, brand voice guidelines, even dietary restrictions for a meal planning project. The more context you give, the less you have to repeat yourself.

![Hand-written index card on a wooden desk labeled CLAUDE.md your project brain with bullet points: tech stack, rules, context, and a lightbulb drawing](Your project brain. The first file to create after installing Claude Code.)

Connect your first MCP server (optional but worth it)

MCP stands for Model Context Protocol. It lets Claude Code connect to external tools: GitHub, Google Drive, Notion, Supabase, Slack, databases, anything with an API.

You don't need MCP to use Claude Code. But once you set up your first server, you'll wonder how you worked without it.

The simplest one to start with is the Git MCP server. It gives Claude Code deeper access to your git history, branches, and diffs beyond what the basic CLI integration offers.

I run 20 MCP servers daily. If you want to go deeper, here's my full breakdown: MCP Servers Explained: The Universal Plug That Connects AI to Everything.

Quick reference: every install method in one place

Mac (terminal):

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

Mac (Homebrew):

brew install --cask claude-code

Windows (PowerShell):

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

Windows (WinGet):

winget install Anthropic.ClaudeCode

VS Code / Cursor: Search "Claude Code" in Extensions (Cmd+Shift+X)

JetBrains: Install from JetBrains Marketplace

Then in any project:

cd your-project
claude

If you're not sure which Claude product you need, or whether Claude Code is even the right tool for your use case, start with that guide. It covers all five Anthropic products and when to reach for each one.

That's it. Three minutes to install. A lifetime of "how did I ever code without this."

TIP: New to Claude Code? Start with VS Code. Get comfortable. Then move to Ghostty when you want more control. The install is the same either way.