Getting Claude Code on a Mac running takes about two minutes and a single command, with no Node.js to wrangle and no version conflicts to untangle. The native installer drops a self-contained binary onto your machine, wires up your PATH automatically, and keeps itself updated in the background. You sign in once with a Claude Pro or Max subscription and you are coding from the terminal straight away.

Quick Answer

Run the native install command in Terminal, restart the terminal, type claude to launch it, then authenticate against your Claude Pro or Max account on first run. It needs macOS 13 Ventura or newer and works on both Apple Silicon and Intel Macs. No Node.js required.

What you need before you start

The native installer asks for very little. You want macOS 13.0 Ventura or later, although Claude Code itself runs back to macOS 10.15 Catalina, which covers nearly every Mac from 2019 onward. Allow around 300MB of free disk space, and while 4GB of RAM is the floor, 8GB or more makes large codebases far more comfortable. You also need an active Claude Pro or Max subscription, since Claude Code authenticates against your plan rather than a separate licence key. The binary is signed by Anthropic and notarised by Apple, so you will not see any Gatekeeper warnings on launch. If you are buying or building a machine for serious AI and development work, the AI PC range at Evetech is geared exactly for this kind of workload.

Install Claude Code step by step

  1. Open Terminal. You will find it in Applications, then Utilities, or just search for it with Spotlight.
  2. Confirm Claude Code is not already installed by typing claude --version. If you get "command not found", you are clear to install.
  3. Run the official native installer command from the Claude Code documentation. The script downloads the binary, places it at ~/.local/bin/claude, and adds that location to your PATH for you.
  4. Close Terminal completely and reopen it so the updated PATH takes effect. This step trips up a lot of first-timers who skip it.
  5. Type claude and press Enter. On first launch it opens a browser window to sign in.
  6. Log in with the Claude account that holds your Pro or Max subscription and approve the access request. The terminal confirms you are authenticated.
  7. Move into a project folder with cd, run claude again, and start giving it instructions.

Why the native installer is the right choice

On macOS you can install through Homebrew or npm as well, but the native binary is the cleanest path for most people. It carries no dependency on Node.js, so you never hit a version mismatch between the tool and your runtime. It self-updates in the background, which means you stay current without manual upgrades. And it installs to your user directory, so it does not need admin rights or system-wide changes. Developers running other coding tools and AI workloads tend to gravitate to capable, well-cooled machines, and the best-selling PCs at Evetech give you a sense of what most buyers pair with this kind of software.

Setting up Git and your first project

Claude Code uses your Git history to understand a project's context, so a repository is the natural starting point. If you have not already initialised Git in your project folder, run git init and make at least one commit before you launch claude. With a repo in place, Claude Code can read recent commits, understand what changed, and reason about the project's structure rather than treating it as a blank directory.

Once inside a session, a CLAUDE.md file at the project root acts as standing instructions for the agent: team conventions, which files to avoid, or any domain context it should know. Creating one is optional but makes a measurable difference on larger codebases because every new session starts with that context already loaded rather than having to be explained again.

Using Claude Code with an IDE

Claude Code is a terminal tool, but it pairs cleanly with any editor. The VS Code extension and the JetBrains plugin both embed a Claude Code terminal panel directly in the IDE so you can talk to the agent without switching windows. If you prefer a standalone terminal, iTerm2 or Warp work well because both support rich output formatting. Whichever setup you choose, the agent reads and writes files directly on your filesystem, so there is no project import step and no separate sync.

Frequently Asked Questions

Do I need Node.js to install Claude Code on a Mac?

No. The native installer is fully self-contained and does not depend on Node.js. That is the main reason it is the recommended method on macOS, since it removes a common source of version conflicts.

Which Claude plan do I need?

Claude Code authenticates against a Claude Pro or Max subscription. You sign in on first launch and the tool draws on your plan, so there is no separate licence key to enter.

Does it work on Intel Macs or only Apple Silicon?

Both. The native installer supports Apple Silicon and Intel machines. You want macOS 13 Ventura or newer for the smoothest experience, though Claude Code runs back to Catalina.

Where does the binary get installed?

The installer places the claude binary at ~/.local/bin/claude and adds that folder to your PATH automatically. After you reopen Terminal, the claude command works from anywhere.

Why does claude say "command not found" after installing?

Almost always because the terminal session has not picked up the new PATH yet. Quit Terminal entirely and reopen it, then try claude again. A fresh session loads the updated PATH.

Setting up a machine for AI-assisted coding? Explore the AI PC range at Evetech for hardware tuned to run modern developer and AI tools without breaking a sweat.