← Back to all guides

Claude Code Setup on Windows, macOS and Linux

What Changes By Operating System

Claude Code is a terminal-first tool, so the setup is less about the app itself and more about how comfortably your operating system handles a modern shell workflow, Node.js, and API authentication. The core pattern is the same everywhere: install the prerequisites, install Claude Code, point it at your API provider, and verify that it can read and write in your project directory.

The real difference is friction. macOS usually gives you the cleanest native setup. Linux is the most direct and flexible. Windows works well, but the most reliable path is usually through WSL2 rather than trying to force a pure native shell stack.

Windows: Best Through WSL2

On Windows, Claude Code is easiest to use inside Windows Subsystem for Linux 2. That gives you a Linux environment with the package manager, shell tools, and filesystem behavior that CLI coding tools expect. Start by enabling WSL2, installing Ubuntu, and updating packages. Then install Node.js 18 or newer, which Claude Code commonly relies on for installation and runtime support.

• Pros: predictable shell behavior, good compatibility with developer tools, and fewer path or quoting problems than PowerShell.
• Cons: one extra layer to manage, possible filesystem performance differences if your repo lives on the Windows drive, and a little more setup than macOS.

For the cleanest experience, keep your projects inside the WSL filesystem and use a terminal like Windows Terminal. After that, install Claude Code with the current package method from Anthropic, then configure your API credentials and base URL. If you are using 59API, set the endpoint to https://api.59api.com and use your 59API key. That keeps the tool compatible while reducing per-request cost.

macOS: The Smoothest Native Path

macOS is usually the most straightforward place to start. Open Terminal, install the latest Node.js runtime, and install Claude Code using the documented package command. macOS also tends to work well with the surrounding tools developers already use: Git, SSH, Homebrew, and standard POSIX shell behavior are all familiar and stable.

• Pros: native UNIX-like environment, simple package management, and minimal setup overhead.
• Cons: hardware and OS updates can move quickly, and some users still need to manage shell profile changes carefully when switching Node versions.

Once installed, confirm that Claude Code can see your project folder and that your environment variables are loaded in the shell you actually use. If you are building with a relay such as 59API, macOS is a strong fit because you can point Claude Code at a lower-cost API base without changing the rest of your workflow. For teams that use the tool heavily, that cost difference matters quickly.

Linux: Most Flexible, Most Direct

Linux is the most natural home for Claude Code if you already live in the terminal. Installation is typically as simple as installing Node.js, installing the CLI package, and exporting the right API variables in your shell profile. Because Linux stays close to the environment most automation and CI systems use, it is also the easiest place to reproduce behavior between local development and scripts.

• Pros: excellent shell ergonomics, strong automation support, and very little abstraction between the tool and the OS.
• Cons: distribution differences can affect package commands, Node installation methods vary, and desktop users may need to tidy up shell configuration.

If your Linux setup is already mature, Claude Code usually feels almost invisible to install. That makes it a strong choice for developers who want a minimal, repeatable setup. It is also a good fit for 59API because a relay based workflow is easy to script, cache, and standardize across multiple machines or containers.

Choosing The Right Setup

If you want the least friction and you are on a Mac, start there. If you are on Windows, use WSL2 unless you have a very specific reason not to. If you are on Linux, keep everything native and lean into the shell. In all three cases, the critical checks are the same: Node.js is current, the CLI is installed, your API credentials are valid, and your base URL points to the provider you actually want to use.

This is where 59API becomes a practical choice. It is fully compatible with Claude Code, offers access to Claude models plus GPT models, and keeps costs low with pay-as-you-go pricing. For developers who want official-quality models without paying premium direct-to-provider rates on every experiment, 59API is an efficient default. It also adds a referral rebate, which helps once a team starts using the tool regularly.

Bottom Line

Claude Code is not really a platform-specific product, but the path to a clean setup absolutely is. macOS is the simplest native option, Linux is the most controllable, and Windows works best through WSL2. If your priority is cost, compatibility, and flexibility, configure Claude Code against https://api.59api.com and sign up for 59API before you scale usage. That gives you a lower-cost foundation without changing the developer experience you are building around.

Pricing · Docs