How to Set Up Claude Code on a Mac: Full Developer Environment Guide
A step-by-step guide to installing Claude Code, Zed, T3 Code, and Bamboo on a fresh Mac for a complete AI coding workflow.
What’s the simplest way to set up Claude Code on a Mac?
The simplest working setup is a Claude Pro subscription ($20 a month, or roughly $16.67 a month billed annually) paired with the official Claude Code command line tool and a free editor like Zed. That combination alone gives you a functioning AI coding environment: an agent that can read and edit files in a real project, plus a place to inspect and fix code by hand. Everything else, like T3 Code or Bamboo, is an optional layer on top for managing multiple tasks or agents at once.
TL;DR
- Claude Pro at $20 a month includes Claude Code access, and it’s the right starting point before jumping to Max plans or team seats.
- Max 5x and Max 20x ($100 and $200 a month) increase your per-session usage allowance, not your weekly limits by the same multiple, and they’re monthly-only plans.
- Your Claude chat and Claude Code usage draw from the same subscription pool, so opening more terminals or switching tools doesn’t create extra capacity.
- A clean Mac setup needs Xcode command line tools, Homebrew, Git, GitHub CLI, and Node.js LTS before Claude Code itself goes in.
- Zed is a free editor that can run Claude Code in its built-in terminal or connect to it directly through the agent client protocol (ACP).
- T3 Code is free and open source and gives Claude Code a dedicated task interface with work trees, diffs, and pull request creation.
- Bamboo costs $20 a month on top of your Claude subscription and adds a task board plus multi-agent coordination, but it’s still in alpha.
Run it on our own servers.
✓SOC 2 and HIPAA from day one.
✓Log every action.
✓Only the right people get in.
✓
How much does Claude Code actually cost?
Claude Code isn’t a separate subscription. It’s a feature included in existing Claude plans, and the free tier doesn’t cover it. Pricing breaks down like this:
- Pro: $20/month, or $200/year (about $16.67/month). This is the entry point for learning, side projects, or figuring out real usage before committing to more.
- Max 5x: $100/month. Increases per-session usage compared to Pro, but doesn’t guarantee a 5x increase across every weekly limit.
- Max 20x: $200/month. Same idea, larger allowance, still monthly only.
- Team Standard: $25/person/month, or $20/person/month billed annually, starting at two seats.
- Team Premium: $125/person/month, or $100/person/month billed annually, mainly offering more usage.
- Enterprise: $20/person/month billed annually as a published seat price, with usage billed separately at API rates. Self-serve starts at 20 seats, sales-assisted at 50.
Both Pro and Max run on 5-hour session limits plus weekly caps, and critically, chat usage and Claude Code usage share the same allowance. Switching between tools or opening parallel terminal sessions doesn’t give you more room to work.
There are also monthly API credits rolling out for Max and Team plans (Max 5x gets $100, Max 20x gets $200, Team gets a seat-based pool), claimed by linking a console organization after seven days on an eligible plan. These credits don’t cover interactive Claude Code sessions or extra usage once you hit your plan’s limit, and Pro doesn’t include this benefit at all.
For a first setup, sticking with a standard Pro subscription and signing in normally keeps billing simple and predictable.
What do you need to install before Claude Code?
Before Claude Code goes on the machine, a few standard developer tools need to be in place:
- Xcode command line tools. Run
xcode-select --installin Terminal. You don’t need the full Xcode app for a basic web project. - Homebrew. Install it from the official site, run the setup command it gives you, and make sure you also run the path-related follow-up commands it prints, since skipping that step is an easy mistake on a fresh Mac.
- Git and GitHub CLI. Run
brew install git gh. Git tracks changes to your project, and the GitHub CLI (gh) lets Claude work with repositories and pull requests once your account is connected viagh auth loginandgh auth setup-git. - Node.js LTS. Install it from the official Node site. Claude Code itself doesn’t require Node, but most modern web projects and integrations do, so it belongs in the setup anyway.
After these are in place, create a projects folder, a subfolder for your actual app, initialize Git inside it, add a basic README, and make a first commit. That gives any tool you install afterward a real repository and a working branch structure to operate on.
How do you install and sign into Claude Code?
- 1Secure
- 2Regulation-compliant
- 3Auditable
- 4Scalable
Claude Code installs through a native macOS command from Anthropic’s official setup page. After installation finishes and any path instructions are followed, open a new terminal window and confirm it worked with a version check. Then authenticate with claude /login, signing in with the same account tied to your subscription.
Once inside a project folder, running claude starts a session. The /status command inside that session shows which account and authentication method is active, which matters if you’ve previously configured an API key: an API key can silently switch you to API billing instead of your subscription. If the install misbehaves, a built-in doctor command can diagnose common issues. The native installer also updates itself automatically, so there’s no need to manually reinstall to stay current.
A simple first test, like asking Claude to explain the files in your project folder, confirms it’s reading the right directory and that your README is visible.
Which editor pairs best with Claude Code?
Zed is a solid choice here because it’s free, lightweight, and gives you two separate ways to work with Claude. You can open Zed’s built-in terminal and run the Claude Code CLI directly, or you can use Zed’s agent panel through the agent client protocol (ACP), which lets the editor display an external coding agent’s work inline.
To set up the ACP integration, open the command palette, install the Claude agent integration through Zed’s extension registry, and start a new agent thread, logging in with your Claude subscription if prompted. It’s worth double-checking that you’ve selected the external Claude agent specifically, since Zed also offers its own AI features through Anthropic models under a separate billing arrangement. Seeing “Claude” in a model picker doesn’t automatically mean your Pro subscription is paying for it.
For many people, Claude Code plus Zed is a complete enough setup to stop at.
Is it worth adding T3 Code or Bamboo on top?
It depends on whether you want a dedicated interface for managing multiple coding tasks.
T3 Code is free and open source. It wraps Claude Code in a workspace built around agent conversations, file changes, and Git operations, using your existing Claude login rather than requiring a new one. You can install the desktop app via Homebrew (brew install --cask t3-code) or run a browser version with npx. Its most useful feature for beginners is supervised permissions, which lets you see and approve changes before they’re applied, and “work trees,” which give each task its own branch and folder so parallel tasks don’t collide. For a first project, starting with a single task before adding a second is the more manageable approach.
Bamboo goes further, acting as a native desktop workspace that supports Claude Code alongside other tools like Codex, OpenCode, and others. It adds a task board (pending, in-progress, review stages), file diffs, and visual references for UI work. Its more advanced feature is an “architect and workers” setup, where one agent plans and coordinates while up to three others handle separate pieces of work, which can be saved as a reusable team profile. Bamboo costs $20 a month for two personal devices, on top of whatever Claude subscription or other provider usage you’re already paying for, so a monthly Pro plan plus Bamboo runs about $40 a month before tax. It’s still in alpha, so bugs and changes should be expected.
Delta, from the team behind Zed, is a related but different option: it ties conversations to code changes via a version history system and is currently in public beta. The catch is that direct Claude subscription sign-in isn’t yet supported there, it’s listed as “coming soon,” so using it with a Claude subscription today isn’t straightforward. It also uploads tracked project files to its servers, which is worth knowing before pointing it at a private repository. Until native Claude sign-in lands, Zed’s external agent integration or T3 Code is the more direct route for this particular setup.
Frequently Asked Questions
Do I need Claude Max to use Claude Code seriously?
No. Claude Pro at $20 a month includes Claude Code and is a reasonable starting point for learning or side projects. Moving to Max 5x or Max 20x makes sense once Pro’s session limits regularly interrupt real work, not before.
Does running Claude Code in multiple tools give me more usage?
No. Claude chat and Claude Code usage draw from the same subscription allowance. Opening another terminal, switching to T3 Code, or adding Bamboo doesn’t create additional capacity.
Is Zed’s AI subscription the same as my Claude subscription?
No. Zed has its own paid hosted AI features that are billed separately. Using your Claude subscription through Zed’s external agent integration (via ACP) doesn’t require a Zed AI subscription at all.
What’s the difference between T3 Code and Bamboo?
T3 Code is free and open source, focused on giving Claude Code a task and review interface. Bamboo costs $20 a month and adds a task board, multi-agent “architect and workers” coordination, and visual references, but it’s still in alpha.
Can I use my Claude subscription inside Delta?
Not yet directly. Delta’s documentation currently lists native Claude subscription sign-in as “coming soon.” You can connect an Anthropic API key instead, but that’s separate, usage-based billing rather than your subscription.
