Quick Summary: Claude Code can be installed via native installers on macOS, Windows, and Linux from the official Claude Code website. Windows users must install WSL2 first before running Claude Code. After installation, authenticate with your Claude account when Claude Code opens a browser window for you to log in on first launch to start coding with AI assistance directly from your terminal or desktop app.
Claude Code represents Anthropic’s push into agentic AI development tools. This command-line assistant reads codebases, edits files, runs commands, and integrates with development workflows.
But getting it installed isn’t always straightforward. Different platforms require different approaches. Windows needs extra setup. And the documentation, while comprehensive, can overwhelm newcomers.
This guide cuts through the complexity. It covers system requirements, platform-specific installation steps, authentication, and verification—everything needed to get Claude Code running properly.
System Requirements Before Installation
According to the official Claude Code documentation, the tool supports macOS, Windows, and Linux. However, each platform has specific prerequisites.
For macOS, the requirements are minimal. The system needs macOS 13.0 or later. Both Intel and Apple Silicon chips work fine.
Windows presents more complexity. The operating system must be Windows 10 Build 19041 or later, or Windows 11. But here’s the catch—Claude Code doesn’t run natively on Windows.
Windows Subsystem for Linux 2 (WSL2) is mandatory. This creates a Linux environment where Claude Code actually operates. Without WSL2, installation fails.
Linux users need a 64-bit distribution. The official documentation confirms support for Ubuntu, Debian, Fedora, and other major distributions. Alpine Linux and musl-based systems require additional configuration.
All platforms need a stable internet connection during installation. The download sizes vary but typically range from 50MB to 500MB depending on what’s already installed.
| Platform | Minimum Version | Special Requirements |
|---|---|---|
| macOS | 13.0 | None |
| Windows | 10 Build 19041 or 11 | WSL2 required |
| Linux | 64-bit distribution | glibc-based preferred |
Installing Claude Code on macOS
The macOS installation process uses a native installer. This is the simplest path among all platforms.
First, download the installer from the official Claude Code website. The download page automatically detects macOS and offers the appropriate package.
Open the downloaded .dmg file. Drag the Claude Code application to the Applications folder. Standard macOS installation—nothing unusual here.
Some users encounter a security prompt when first launching. macOS blocks apps from unidentified developers by default. Right-click the Claude Code application and select “Open” to bypass this one-time warning.
The command-line tool installs automatically with the desktop application. Open Terminal and type claude –version to verify. If the version number appears, installation succeeded.
Verifying macOS Installation
Run these commands to confirm everything works:
| claude –version claude –help |
Both commands should return output without errors. The version command shows the installed Claude Code version. The help command displays available options and commands.
Creating a test directory helps verify full functionality. Navigate to a project folder and run claude to start an interactive session. The tool should initialize and prompt for authentication if not already logged in.
Windows Installation With WSL2
Windows installation requires multiple steps. The process takes longer than macOS but remains manageable.
WSL2 must be installed first. Open PowerShell as Administrator and run:
| wsl –install |
This command installs WSL2 and Ubuntu by default. The system will require a restart. After rebooting, Ubuntu launches automatically to complete initial setup.
Create a Unix username and password when prompted. These credentials are separate from Windows login credentials.
Once WSL2 is running, the Linux installation process applies. Open the Ubuntu terminal (installed with WSL2) and download the Claude Code installer for Linux.
Installing Claude Code in WSL2
According to the official documentation, the installation command downloads and runs the native installer:
| curl -o- raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash |
This script handles dependencies automatically. It installs Node.js if needed, sets up the Claude Code binary, and configures PATH variables.
The installation takes a few minutes. Progress bars and status messages indicate what’s happening. When complete, close and reopen the terminal to refresh environment variables.
Testing the installation follows the same process as macOS. Run claude –version to verify.
Linux Installation Process
Linux users have the most straightforward installation path. The native installer works directly without additional layers like WSL2.
Download and run the installation script:
| curl -fsSL claude.ai/install.sh | bash |
This downloads the Claude Code binary, installs dependencies, and configures the shell environment. The script detects the distribution and adjusts accordingly.
For Ubuntu and Debian-based systems, the script configures installation. The official documentation confirms support for Ubuntu 20.04+, Debian 10+, and other distributions.
Alpine Linux Considerations
Alpine Linux and musl-based distributions need extra steps. The official documentation notes these systems require manual configuration.
The standard installer may fail on Alpine. Instead, download the musl-compatible binary directly from the releases page. Extract it to a directory in the system PATH, typically /usr/local/bin.
Set executable permissions:
| chmod +x /usr/local/bin/claude |
Alpine users should verify compatibility before proceeding. Some features may not work identically to glibc-based distributions.
Authentication and Account Setup
After installing Claude Code, run claude in your terminal. On first launch, Claude Code opens a browser window for you to log in.
This opens the Claude authentication page. Sign in with an existing Claude account or create a new one.
The browser displays an authorization code. Copy this code and return to the terminal. Paste the code when prompted.
Successful authentication stores credentials locally. Future sessions won’t require login unless credentials expire or are manually cleared.
Team and Enterprise Authentication
According to the official authentication documentation, teams using Claude for Teams or Enterprise have additional options. Organizations can configure single sign-on (SSO) or cloud provider authentication.
SSO setup requires administrator configuration. Individual developers then authenticate through their organization’s identity provider rather than personal Claude accounts.
Cloud provider authentication works for AWS, Google Cloud, and Azure deployments. This method uses existing cloud credentials instead of separate Claude accounts.
| Authentication Method | Use Case | Setup Complexity |
|---|---|---|
| Personal Account | Individual developers | Simple |
| Teams/Enterprise SSO | Organizations | Requires admin |
| Cloud Provider | AWS/GCP/Azure users | Moderate |
Desktop App Installation
Claude Code offers both command-line and desktop applications. The desktop app provides a graphical interface while maintaining full terminal functionality.
Download the desktop installer from the official Claude website. The page offers macOS, Windows, and Windows ARM64 versions. Select the appropriate version for the system.
macOS installation follows the same .dmg process described earlier. Windows users can download the desktop app for a graphical interface without requiring WSL2 setup.
The desktop app includes integrated terminal access. It can launch Claude Code sessions without switching to external terminal applications.
One advantage of the desktop app is background availability. According to the official download page, the app ‘stays ready in the background’ and can be brought up from any app without switching windows or losing focus.
Use Get AI Perks to Find Credits for Your Claude Code Stack
Installation is the easy part. The real cost usually comes from everything around it: infrastructure, supporting tools, and paid services used during setup and testing. Get AI Perks can help by listing startup credits and discounts in one place, along with guidance on how to apply.
With Get AI Perks, you can:
- Find credits for cloud and AI-related tools
- Check perk conditions before applying
- Avoid wasting time on offers you may not qualify for
- Lower the cost of getting your setup in place
Visit Get AI Perks to see whether the available offers match the tools you plan to use with Claude Code.
IDE Extensions and Integrations
Beyond standalone installation, Claude Code integrates with popular development environments. Extensions exist for Visual Studio Code and JetBrains IDEs.
The VS Code extension installs through the marketplace. Search for “Claude Code” in the Extensions panel and click Install. The extension requires the command-line tool to be installed first.
Some users report issues with the bundled VS Code extension file. If the automatic installation fails with an “End of central directory record signature not found” error, the bundled .vsix file may be corrupted.
The workaround involves installing the extension manually from the VS Code marketplace rather than relying on the CLI’s bundled version. This separates the two components and prevents installation conflicts.
JetBrains integration works similarly. Install the plugin from the JetBrains marketplace within IntelliJ IDEA, PyCharm, WebStorm, or other JetBrains products.
Verifying Installation Success
Proper verification ensures Claude Code works correctly before starting actual development tasks.
Basic verification checks command availability:
| claude –help claude –version |
These commands should execute without errors. The help command lists available options. The version command shows the installed release.
Functional testing requires starting a session. Create a test directory:
| mkdir test-project cd test-project claude |
This initializes an interactive Claude Code session. The tool should analyze the directory (empty in this case) and present a prompt.
Try basic commands within the session. Type help to see available actions. Request simple tasks like “create a README file” or “explain what you can do.”
Successful responses indicate proper installation. If errors occur, they typically relate to authentication, network connectivity, or missing dependencies.
Update and Version Management
Claude Code updates automatically by default. The official documentation explains that the tool checks for new versions and installs them without user intervention.
Update behavior can be configured through Claude Code settings. The official documentation covers release channel configuration and manual update options.
Manual updates require running the installation script again. The same command used for initial installation pulls the latest version:
| curl -fsSL claude.ai/install.sh | bash |
Installing specific versions is possible for testing or compatibility reasons. The advanced setup documentation covers version pinning and release channel configuration.
Release channels include stable, beta, and nightly. Stable is recommended for production work. Beta and nightly channels provide early access to new features but may contain bugs.
Common Installation Problems
Several issues appear frequently in community discussions about Claude Code installation.
PATH configuration causes many problems. If the claude command isn’t found after installation, the binary directory isn’t in the system PATH.
On macOS and Linux, adding the directory to PATH typically involves editing ~/.bashrc, ~/.zshrc, or similar shell configuration files. The installation script usually handles this automatically, but manual verification helps troubleshoot.
Windows users in WSL2 may need to close and reopen the terminal after installation. The environment variables don’t refresh in existing sessions.
Network restrictions block some installations. Corporate firewalls or proxy servers may prevent downloading the installer or connecting to authentication servers.
Proxy configuration requires environment variables:
| export HTTP_PROXY= proxy.example.com:8080 export HTTPS_PROXY= proxy.example.com:8080 |
Permission errors occur when installing to protected directories. The installer needs write access to /usr/local/bin or equivalent locations. Running with sudo resolves this but should be avoided unless necessary.
Frequently Asked Questions
Can Claude Code run without an internet connection?
No. Claude Code requires internet connectivity to function. The tool sends code and queries to Anthropic’s servers for processing. Local caching may allow some operations to work temporarily offline, but full functionality requires active connection.
Does Claude Code work with existing AI coding tools?
Yes. Claude Code can run alongside GitHub Copilot, Cursor, or other AI development tools. They operate independently and don’t conflict. However, using multiple AI assistants simultaneously may create confusion about which tool is handling which task.
Is WSL2 required for all Windows features?
The command-line tool requires WSL2 on Windows. However, the desktop application runs natively on Windows without WSL2. The desktop app provides similar functionality through a graphical interface rather than pure command-line interaction.
How much does Claude Code cost to use?
Pricing varies based on usage and subscription tier. Check the official Claude website for current pricing, as costs and plan structures change over time. Some features require Claude Pro or Enterprise subscriptions.
Can Claude Code edit files outside the project directory?
By default, Claude Code restricts file access to the current project directory for security. Configuration settings can expand permissions, but doing so requires explicit authorization. The sandboxing documentation covers permission management in detail.
What’s the difference between Claude Code and the Claude API?
Claude Code is a development tool for interactive coding assistance. The Claude API provides programmatic access for building applications that use Claude’s AI capabilities. They serve different purposes—one for developers writing code, the other for applications integrating AI features.
Does uninstalling remove all Claude Code data?
Uninstalling removes the application binary but may leave configuration files and cached data. Complete removal requires manually deleting the ~/.claude directory on macOS and Linux, or the equivalent AppData location on Windows.
Getting Started After Installation
With Claude Code installed and verified, the next step involves understanding how to use it effectively.
The quickstart documentation recommends starting with simple tasks. Navigate to an existing project and run claude to begin an interactive session.
Ask Claude to explain the project structure. Request a summary of what the codebase does. These exploratory queries help understand how the tool interprets code.
Try making small changes. Ask Claude to add comments to functions, create simple test files, or refactor basic code blocks. These tasks demonstrate editing capabilities without risk.
Git integration works automatically if the project uses version control. Claude Code can create commits, explain diffs, and suggest improvements based on changes.
The official documentation includes workflow examples for common development tasks. These cover bug fixing, feature implementation, code review, and automated testing.
Claude Code is an evolving tool. Installation is just the foundation. Understanding its capabilities, limitations, and best practices takes experimentation and practice.
Ready to install Claude Code? Download the appropriate installer for your platform from the official website and follow the steps outlined in this guide. Authenticate with your Claude account, verify the installation works correctly, and start exploring AI-assisted development.
