How to run Claude Code for a whole team: your options compared

• Most teams should start with the Claude Team plan. Every seat includes Claude Code, and you can commit shared settings to your repository^{1, 7}.
• Add cloud sessions when work should keep running after a laptop closes or teammates need to read a session².
• Use an organization-shared environment so everyone's cloud sessions start from the same setup³. Use a self-hosted one (public beta) if code must run on your own machines⁴.
• Add Claude Tag if your team hands work to Claude from Slack channels⁵.
• Pay through the Claude Console if you prefer API billing over seats, but note that cloud sessions need a claude.ai sign-in⁸.
• Leverage Computer if your team already runs Claude Code every day and wants to run much more of it at once. Sessions live in shared team threads, keep going with laptops closed, start from a webhook, a pull request or a schedule, and every tool call goes through rules you set^{10, 11, 16, 12}.

1. Billing and access. Seats or usage, and who can turn what on.
2. Shared setup. The same instructions, permissions and tools for everyone.
3. Where the agent runs. A laptop, Anthropic's cloud, your own servers or a shared computer, and whether it keeps working when nobody is at a keyboard.
4. Seeing each other's work. Can a teammate read, join or continue a session?
5. Control. Spend limits, approvals and a record of what the agent did.

Claude Team plan: the default for most teams

Strengths

• Every Team seat includes Claude Code and Claude Cowork, for teams of 2 to 150¹.
• Anthropic recommends it for most teams: members get Claude Code and Claude on the web "with centralized billing and team management"⁸.
• Shared setup lives in your repository: commit .claude/settings.json "so everyone who clones the repository gets the same permissions, hooks, and plugin settings"⁷. Admins can enforce managed settings that personal settings cannot override⁷.

Weaknesses

• By default each session runs on one person's machine and stays with that person.
• Usage limits apply per seat; Premium seats give five times the usage of Standard¹.

Price. Standard $20 per seat a month billed yearly or $25 monthly; Premium $100 or $125. Enterprise is $20 per seat a month plus usage at API rates, billed yearly with a 20-seat minimum¹.

Claude Code cloud sessions: for work that should continue after the laptop closes

Strengths

• "The session keeps running after you close your laptop, and you can check on it or steer it from any device"².
• No separate charge for the VM; it counts toward your plan's usage².
• On Team and Enterprise, a session can be shared with Team visibility so other members of your organization can open it².
• An Owner can create environments "shared with every member of the organization", so the team standardizes on one setup³.

Weaknesses

• Cloning and pull requests in Anthropic-hosted environments need GitHub².
• A shared session is a snapshot: recipients' "view doesn't update in real time"².
• Sessions stop after a period of inactivity and the VM is reclaimed². The VM has about 4 vCPUs, 16 GB of RAM and 30 GB of disk, and large builds can be stopped³.

Price. Included with Pro, Max, Ultra and Team plans, and Enterprise premium or Chat + Claude Code seats².

Self-hosted environments: when code must run on your own machines

Strengths

• Cloud sessions run "on infrastructure your organization operates", like a self-hosted CI runner, and "Anthropic never connects into your network"⁴.

Weaknesses

• "Public beta on Team and Enterprise plans and are off by default"⁴.
• "Session content still goes to api.anthropic.com", and you run and maintain the machines⁴.

Price. Uses your organization's Claude Code usage⁴; you pay for your own infrastructure.

Claude Tag in Slack: for teams that hand work over in Slack

Strengths

• Anyone in a channel can tag @Claude and hand it work, such as reproducing a bug and opening a pull request⁵.
• Slack users don't each need a Claude seat; channel work is billed by usage under a spend limit an Owner sets⁵.

Weaknesses

• Public beta, Team and Enterprise only, and Slack only⁵.
• Each conversation runs in a sandbox that "is discarded when the conversation goes idle"⁵.

Price. Usage-based, drawn from an organization balance⁵.

Claude Console (API billing): for teams that want usage billing instead of seats

Strengths

• An official option "for organizations that prefer API-based billing", with a role that can only create Claude Code API keys⁸.

Weaknesses

• Cloud sessions need a claude.ai sign-in and "always use your subscription credentials"⁸.
• Claude on the web, with centralized team management, comes with the Team and Enterprise plans, not with Console keys⁸.

Price. API usage rates⁸.

GitHub Codespaces: if you want a cloud dev box per developer

Strengths

• A full cloud development environment per person, billed by the hour⁹.

Weaknesses

• Organizations get no free quota, and you still need a Claude plan or API key inside the codespace⁹.
• Each codespace belongs to one person, so the team does not share sessions.

Price. $0.18 an hour for a 2-core machine up to $2.88 for 32 cores, plus $0.07 per GB-month of storage⁹.

Leverage Computer: for teams that run Claude Code or Codex every day and want to run much more of it

We make Leverage Computer. This section uses our own public pages, and it says where Leverage Computer does not fit.

Leverage Computer runs Claude Code, Codex and Grok Build sessions in a shared workspace. Each session gets its own VM with sudo, a terminal, a browser and a persistent disk^{10, 14}.

Strengths

• Multiplayer sessions. Watch a teammate's session live, steer it, queue a message or stop it. Share a session with a space, the workspace, or people as viewers or collaborators¹¹.
• Keeps working with laptops closed. A VM sleeps when idle and costs nothing asleep¹⁰.
• Use your Claude plan. Connect Claude, ChatGPT or Grok plans or API keys, and pool several accounts¹⁴.
• Approvals on tool calls. By default, reads run, and sends, deletes and deploys wait for a person; every call is recorded¹².
• Team memory in Git. Instructions, memory and skills live in Git folders that every session opens with¹⁵.
• Your own environments. Set variables and secrets and pick them per space or session. A secret can be added to HTTPS headers by the network, so its value never enters the VM¹⁰.
• PR Auto-fix. Turn it on for a pull request, and the agent fixes failed checks, answers review comments and resolves merge conflicts until it is merged or closed¹⁵.

Where Leverage Computer is the wrong choice

• One developer working alone. A Claude plan on your laptop is simpler and cheaper.
• Code that must run on your own servers. Leverage Computer does not offer a self-hosted version; look at Anthropic's self-hosted environments.
• Repositories outside GitHub. Session checkouts and pull requests are built for GitHub¹⁵.
• A fixed monthly bill. You pay for agent hours, plus AI usage if you pay for it from Leverage credits, so cost moves with use¹³.

Price. $0.50 per agent hour on a Standard machine (2 CPUs, 4 GB), $1.00 Medium, $2.00 Large. People and storage are free. AI comes from your own plan, an API key, or credits at the provider's cost plus 20%^{13, 10}.

Inside one Leverage Computer session

People

Watch it live

Steer or queue a message

Approve tool calls

Share as viewer or collaborator

Environment

Variables per space or session

Secrets added at the network

Values hidden from transcripts

The computer

Its own VM with sudo

Claude Code, Codex or Grok Build

Sleeps when idle

terminalbrowserfilesdisk

Git

Every turn committed

Team memory and skills

What it makes

Pull requests with Auto-fix

Private preview links

Published pages

Scheduled and event runs

• Agent teams coordinate several Claude Code instances, with one session as the lead. They are experimental, off by default, and use "significantly more tokens than a single session"⁶. They help one person split work, not several people share it.

1. Start with Team seats and a committed .claude/settings.json. That covers most teams^{1, 7}.
2. Need work to continue while people are away? Turn on cloud sessions and an organization-shared environment^{2, 3}.
3. Need several people on one live session, a lasting computer, or approvals before agents act? Compare Leverage Computer^{10, 11, 12}.

• How to share Claude Code sessions with your team
• Ways to run Claude Code in the cloud, so it keeps working when your laptop is closed
• Codex for teams: your options compared
• Every harness, one workspace
• The computer underneath
• Pricing
• All comparisons