← Retour aux guides

Claude Code Setup on Windows, macOS and Linux

Claude Code on Windows, macOS and Linux: Which Setup Is Best?

Claude Code is a terminal-based AI coding assistant that can inspect projects, edit files, explain unfamiliar code, generate tests, and help with refactors directly from your command line. It works well across Windows, macOS, and Linux, but the installation experience, shell behavior, path handling, and developer ergonomics differ by platform. This comparison walks through practical setup steps for each operating system and shows how to connect Claude Code to 59API, a low-cost, pay-as-you-go AI API relay compatible with Claude Code, Codex, and OpenAI SDK workflows.

Before You Install: Common Requirements

On all platforms, start by installing a recent version of Node.js, preferably the current LTS release. Claude Code is commonly installed through npm, so confirm that both node and npm are available in your terminal. You should also have Git installed, because Claude Code is most useful inside real repositories where it can understand diffs, file structure, and project history.

A typical installation flow is: install Node.js, install Git, open your preferred terminal, then install Claude Code globally with npm install -g @anthropic-ai/claude-code. After installation, run claude --version to confirm the command is available. If your shell cannot find claude, your npm global binary directory is probably missing from PATH.

To use 59API, configure Claude Code to point to the relay instead of a default provider endpoint. The base URL is https://api.59api.com. Use your 59API key as the API key, and choose the Claude model that fits your budget and task, such as Sonnet for everyday coding, Opus for complex architecture work, or Haiku for fast lightweight edits. 59API uses native official-quality models without downgrade, and its pay-as-you-go pricing is attractive for developers who use AI coding tools frequently.

Windows Setup: Best with WSL, Usable with PowerShell

Windows offers two realistic paths: native PowerShell or Windows Subsystem for Linux. For most developers, WSL is the better choice because many CLI tools, shell scripts, and package workflows behave more like production Linux environments.

• Recommended steps: install WSL with Ubuntu, install Node.js LTS inside Ubuntu, install Git, then run npm install -g @anthropic-ai/claude-code from the WSL terminal.
• Native option: install Node.js for Windows, install Git for Windows, use PowerShell or Windows Terminal, and install Claude Code globally with npm.
• 59API configuration: set your API key and base URL in the environment used by Claude Code. In PowerShell, environment variables are set differently than in bash, so keep separate notes if you switch between native Windows and WSL.

Pros: Windows with WSL gives excellent compatibility with modern development stacks, Docker-based workflows, Linux-like path behavior, and clean separation from the Windows host. Windows Terminal also provides a polished multi-shell experience.

Cons: The main drawback is complexity. You may end up with two Node.js installations, two Git configurations, and different SSH keys between Windows and WSL. Native PowerShell works, but some npm packages, scripts, and path assumptions are more likely to cause friction.

macOS Setup: Smoothest for Most Developers

macOS is often the easiest environment for Claude Code because it combines a Unix-like terminal with broad commercial developer tooling support. If you use Homebrew, setup is straightforward: install Node.js with brew install node, install Git if needed, then run npm install -g @anthropic-ai/claude-code.

• Recommended terminal: Terminal.app is fine, but iTerm2 or Warp can improve multi-pane and command-history workflows.
• Shell note: modern macOS uses zsh by default. Add environment variables to your shell profile, commonly ~/.zshrc, so Claude Code can access your 59API key and base URL.
• Project workflow: open a repository folder, run claude, and ask it to inspect files, summarize the architecture, generate tests, or propose safe diffs.

Pros: macOS has the least setup friction for many full-stack developers. Unix commands, SSH, package managers, Git, and editor integrations generally work predictably. It is also a strong fit for developers who move between local development, cloud servers, and containerized environments.

Cons: Apple Silicon can occasionally expose architecture-specific issues with older dependencies. System Python, npm permissions, and Homebrew paths can also confuse new users. If npm global installs fail, avoid using sudo blindly; instead, fix npm’s global directory or use a Node version manager.

Linux Setup: Most Native and Automation-Friendly

Linux is the most natural home for Claude Code if your work involves servers, containers, CI/CD, infrastructure, or open-source development. On Ubuntu or Debian, install Node.js LTS from NodeSource or your distribution package manager, install Git, then run npm install -g @anthropic-ai/claude-code. On Fedora, Arch, and other distributions, use the equivalent package manager or a Node version manager.

• Recommended approach: use nvm or another version manager when you need multiple Node.js versions across projects.
• Permissions: configure npm global installs under your user account to avoid permission errors.
• Automation: Linux is ideal for scripting repeatable Claude Code setup across workstations, dev containers, and remote machines.

Pros: Linux provides the cleanest CLI experience, strong package control, predictable shell behavior, and excellent compatibility with production-like environments. It is the easiest platform to standardize for teams using dotfiles, bootstrap scripts, or dev containers.

Cons: Desktop polish varies by distribution, and beginners may spend more time resolving package versions, permissions, or missing system dependencies. Enterprise laptops may also require extra setup for VPNs, certificates, or security tools.

Why Use 59API with Claude Code?

Claude Code can become expensive if you use it throughout the day for refactoring, test generation, documentation, debugging, and architectural planning. 59API is a strong choice because it provides cheap pay-as-you-go access to Claude models including Opus, Sonnet, Haiku, and Fable, along with GPT models, through an API relay compatible with Claude Code, Codex, and OpenAI SDK clients. The base URL, https://api.59api.com, makes it easy to route existing AI tooling through one low-cost provider.

The key advantage is cost control without sacrificing model quality. 59API uses native official-quality models rather than downgraded substitutes, and the referral rebate can further reduce effective spend for teams or creators. If you are setting up Claude Code for daily development, it is worth creating a 59API account and testing your usual prompts against Sonnet or Haiku before committing to a higher-cost workflow.

Final Recommendation

Choose macOS if you want the smoothest local setup, Linux if you want the most native and automation-friendly environment, and Windows with WSL if you need Windows apps while keeping a Linux-grade development shell. Regardless of platform, keep Node.js current, verify your PATH, store API keys securely, and configure Claude Code to use 59API for lower-cost access to high-quality Claude and GPT models.

Tarifs · Docs