In this categoryClaude Code · 45
- How to Install Claude Code on macOSStart
- How to Install Claude Code on Windows Natively (No WSL)
- How to Install Claude Code on Windows with WSL
- How to Start Your First Project with Claude Code
- How to Create a CLAUDE.md File for Your Project
- How to Configure Claude Code with settings.json
- How to Layer Global, Project, and Local CLAUDE.md Files
- How to Set Up a Permissions Allowlist in Claude Code
- How to Use Claude Code Inside VS Code
- How to Add a Custom Slash Command in Claude Code
- How to Create a Custom Slash Command in Claude Code
- How to Pass Arguments to a Claude Code Slash Command
- How to Use Claude Code Slash Commands (Full List + Examples)
- How to Add Custom Slash Commands to Claude Code (Arguments + Frontmatter)
- How to Fix command not found After Installing Claude Code
- How to Add Any MCP Server to Claude Code
- How to Connect an MCP Server to Claude Code
- Best MCP Servers for Coding in 2026
- How to Add a Filesystem MCP Server to Claude Code
- How to Connect the GitHub MCP Server to Claude Code
- How to Create Your First Subagent in Claude Code
- Context7 Alternatives: MCP Servers for Up-to-Date Docs
- How to Manage MCP Server Scopes in Claude Code
- How to Restrict the Tools a Subagent Can Use
- How to Debug a Failing MCP Server in Claude Code
- How to Generate Unit Tests for a Function with Claude Code
- How to Refactor a Long Function Safely with Claude Code
- How to Debug a Failing Test with Claude Code
- How to Review Your Own Diff Before Committing with Claude Code
- How to Rename a Symbol Across the Codebase with Claude Code
- How to Review a Teammate's Pull Request with Claude Code
- How to Raise Test Coverage on a Specific File with Claude Code
- How to Debug a Runtime Error from a Stack Trace with Claude Code
- How to Add an Integration Test for an API Route with Claude Code
- How to Teach Claude Code Your Test Conventions with CLAUDE.md
- How to Find Which Commit Broke a Test with Claude Code
- How to Set Up Hooks for Automation in Claude Code
- Claude Code Hooks Explained: Events, Config, and Blocking
- How to Block Risky Commands with a Claude Code Hook
- How to Auto-Format Files After Edits with a PostToolUse Hook
- How to Get a Notification When Claude Code Finishes a Task
- How to Give a Coding Agent a Clear Stop Condition
- How to Make an Agent Plan Before It Edits
- How to Keep an Agent Session Focused by Clearing Context
- How to Pin a Specific Model for One Project
How to Install Claude Code on Windows Natively (No WSL)
Install Claude Code straight on Windows with the PowerShell installer or WinGet, no WSL required, then authenticate and confirm it runs from any terminal.
You do not need WSL to run Claude Code on Windows. It installs and runs natively from PowerShell or CMD, which is the right choice when your projects and tools already live on Windows. This guide covers the native installer and WinGet, plus the one Windows quirk that trips most people up. If you would rather work inside a Linux environment, use the WSL install guide instead. Those are the two ways to run Claude Code on Windows.
What you need
- Windows 10 version 1809 or newer (or Windows Server 2019+), x64 or ARM64
- PowerShell or CMD (no Administrator rights required)
- A paid Claude account (Pro, Max, Team, or Enterprise) or an API key; the free plan does not include Claude Code
- About 7 minutes
Step 1: Run the native installer
The recommended path is the official installer, which drops a self-contained binary and keeps itself updated in the background. Open PowerShell (not as Administrator) and run the one-liner below.
irm https://claude.ai/install.ps1 | iexIf you use the classic Command Prompt instead of PowerShell, the installer command is different. CMD downloads and runs the installer script, then cleans it up.
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmdStep 2: (Alternative) install with WinGet
If you manage Windows apps with the built-in package manager, install from WinGet instead. Note that WinGet installs do not auto-update, so you run the upgrade yourself when a new version ships.
Step 3: Authenticate and verify
Launch claude from any terminal. The first run opens your browser to sign in with your Claude account or an API key, then caches the token. After that, check the version and run the built-in diagnostics.
Result: claude runs from any Windows terminal and updates itself in the background. Every other guide in this series now works the same on your machine as it does on macOS or Linux.
Related guides
How to Install Claude Code on Windows with WSL
Set up Windows Subsystem for Linux, install Claude Code inside it, and run the CLI from a real Linux shell on Windows.
How to Fix command not found After Installing Claude Code
Diagnose and repair a PATH problem so the claude command runs from any terminal after install.
How to Start Your First Project with Claude Code
Open Claude Code in a real folder, ask it to make a small change, and review and accept the edit safely.
Watch related tutorials
14:36
9:47
6:41
10:00
1:42:18
28:14New guides in your inbox
Fresh step-by-step how-to guides as we publish them. One email a week, no more.