Claude Installation and Deployment by Environment

This page is a practical entry point for choosing how to install, run, and deploy Claude Code across local machines, IDEs, cloud sessions, team chat, and CI/CD.

Last checked against the official Claude Code docs: 2026-05-11.

Choose the Right Environment

Environment	Best for	Recommended setup
Local CLI	Terminal workflows, scripting, remote servers, full control	Install Claude Code locally and run claude in the project root
VS Code / Cursor / Windsurf / Kiro	Developers who want visual diffs and editor context	Install the Claude Code extension from the editor marketplace
JetBrains IDEs	IntelliJ, PyCharm, WebStorm and similar IDE workflows	Install the Claude Code plugin from JetBrains Marketplace
Claude Code Desktop	Visual review, parallel sessions, previews, managed setup	Install the desktop app on macOS or Windows
Claude Code on the web	Long-running tasks that continue after you disconnect	Use claude.ai/code with a connected GitHub repository
Slack	Turning team discussions into coding tasks	Install the Claude app and enable Claude Code routing
GitHub Actions / GitLab CI/CD	PR automation, issue triage, scheduled maintenance	Run Claude Code inside CI with repository secrets and workflow files
Enterprise providers	Data residency, procurement, and centralized controls	Use Claude for Enterprise, Anthropic Console, Amazon Bedrock, Google Vertex AI, or Microsoft Foundry

Local CLI Installation

Use the CLI when you want the most complete Claude Code surface: terminal workflows, scripting, local repository access, MCP configuration, and server-side development.

Native Installer

Official docs currently recommend native installation as the default starting point.

macOS, Linux, WSL:

curl -fsSL https://claude.ai/install.sh | bash

Windows PowerShell:

irm https://claude.ai/install.ps1 | iex

Windows CMD:

curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

After installation:

cd /path/to/your-project
claude
/login

Package Managers

Use these when they match your team image, workstation provisioning, or system package policy.

macOS Homebrew:

brew install --cask claude-code

Windows WinGet:

winget install Anthropic.ClaudeCode

Linux package managers are supported for Debian/Ubuntu, Fedora/RHEL, and Alpine through the official Claude Code package repositories. Prefer the official instructions for repository keys and upgrade commands because fingerprints and package channels can change.

npm Installation

Use npm when Node.js is already part of your developer baseline or when package-manager installation is easier to automate.

npm install -g @anthropic-ai/claude-code

Notes:

• Requires Node.js 18 or later.
• Do not install with sudo npm install -g; fix npm permissions or use the native installer instead.
• To upgrade npm installs, use npm install -g @anthropic-ai/claude-code@latest.
• Run claude doctor after installation to verify installation type and version.

Windows, WSL, and Git Bash

For Windows teams, choose one standard path and document it clearly:

Path	When to use	Notes
Native Windows PowerShell	Windows-first teams that do not use Linux tooling	Git for Windows is recommended so Claude Code can use Bash-style tooling when needed
WSL	Teams that develop Linux services on Windows laptops	Install Linux Node/package tools inside WSL, not from the Windows path
Git Bash	Teams that already use Git for Windows heavily	If needed, set CLAUDE_CODE_GIT_BASH_PATH to the Git Bash executable

Common WSL check:

which node
which npm

Both should point to Linux paths rather than /mnt/c/... when you install and run Claude Code inside WSL.

IDE Deployment

Use IDE deployment when the team wants visual review, inline context, and less terminal switching.

VS Code and Compatible Editors

Install the Claude Code extension in VS Code or compatible forks such as Cursor, Windsurf, VSCodium, or Kiro. The extension provides a graphical Claude Code panel, visual diffs, selected-file context, integrated terminal access, and shared settings with the CLI.

Minimum practical checklist:

1. Install the editor extension.
2. Sign in with a Claude account or supported provider.
3. Open a repository folder.
4. Use the Claude Code panel or run claude in the integrated terminal.
5. Keep project rules in CLAUDE.md so both CLI and IDE sessions share context.

JetBrains

Install the Claude Code plugin from JetBrains Marketplace, then restart the IDE. Use it when your team works primarily in IntelliJ IDEA, PyCharm, WebStorm, or related JetBrains IDEs.

Desktop App

Claude Code Desktop is useful when you want graphical workflows: parallel sessions, visual diff review, app preview, integrated terminal/editor panes, and managed setup.

Current deployment note:

• Desktop is available for macOS and Windows.
• Linux desktop users should use CLI, web, or IDE integration instead.
• The desktop app shares the same underlying Claude Code engine and uses the ~/.claude/ configuration area.

Web and Cloud Sessions

Use Claude Code on the web for tasks that should continue while you are offline or away from the terminal. The web version runs on Anthropic-managed cloud infrastructure and requires a connected repository.

Typical setup flow:

1. Open https://claude.ai/code.
2. Sign in with an eligible account.
3. Connect GitHub.
4. Authorize the target repository.
5. Configure setup scripts and environment access if the project requires dependencies, build tools, or network access.
6. Submit a task and review the branch or PR created by Claude.

Use this path for long-running refactors, issue-to-PR workflows, and work that should be monitored from browser or mobile.

Slack Deployment

Claude Code in Slack routes coding-related @Claude mentions into Claude Code sessions on the web.

Team setup:

1. Install or configure the Claude app in Slack.
2. Connect each user to their Claude account.
3. Confirm Claude Code on the web is configured with GitHub access.
4. Invite Claude into the channels where coding tasks are allowed.
5. Choose routing behavior such as code-only or mixed chat/code routing.

Use Slack for bug reports, support escalations, and team discussions that should become tracked code changes.

CI/CD Deployment

Use CI/CD when Claude should respond to repository events instead of a human terminal prompt.

GitHub Actions

Recommended quick path:

claude
/install-github-app

Manual path:

1. Install the Claude GitHub App on the target repository.
2. Add ANTHROPIC_API_KEY or enterprise-provider credentials to repository secrets.
3. Add a workflow file under .github/workflows/.
4. Test with an @claude mention in an issue or pull request comment.

For production workflows, pin permissions, review workflow triggers, and keep human approval on pull requests.

GitLab CI/CD

Typical setup:

1. Add masked CI/CD variables such as ANTHROPIC_API_KEY.
2. Add a Claude job to .gitlab-ci.yml.
3. Decide whether the job is manual, MR-triggered, scheduled, or mention-triggered.
4. Keep Claude changes flowing through merge requests for review.

GitLab CI/CD can also use Amazon Bedrock or Google Vertex AI for enterprise provider requirements.

Enterprise Deployment

For organizations, deployment is not just installation. Decide the operating model first:

Model	Best for	Deployment focus
Claude Team / Enterprise	Most teams that want managed access	Seats, billing, SSO, policy, shared onboarding
Anthropic Console	Developers using API billing	API keys, cost tracking, workspace governance
Amazon Bedrock	AWS-native organizations	IAM, regional access, Bedrock model availability
Google Vertex AI	GCP-native organizations	Workload identity, region, Vertex model configuration
Microsoft Foundry	Azure-native organizations	Enterprise routing, policy, provider setup

Recommended team rollout:

1. Standardize one supported install path per OS.
2. Add repository-level CLAUDE.md with build, test, architecture, and contribution rules.
3. Configure .mcp.json for shared tools when useful.
4. Define allowed tools and security policy before broad rollout.
5. Start with guided usage: codebase Q&A, small bug fixes, tests, and documentation.
6. Move to more autonomous workflows only after review and rollback habits are stable.

Verification Checklist

Run this after installation or deployment:

claude --version
claude doctor
cd /path/to/your-project
claude
/status

Confirm:

• Login works.
• Project files are visible to Claude.
• Git commands work.
• Build and test commands can run.
• Team rules are present in CLAUDE.md.
• MCP servers or connectors are available where expected.

Recommended Training Path

For a mixed team of developers and project managers:

1. Start with local CLI on one demo repository.
2. Add CLAUDE.md and show how project memory changes results.
3. Repeat the same task in VS Code or Desktop so non-terminal users see the visual workflow.
4. Show Claude Code on the web for an issue-to-PR flow.
5. Show Slack or CI/CD only after the local workflow is understood.
6. End with permissions, secrets, review policy, and rollback discipline.

Official Sources

• Claude Code quickstart
• Advanced setup and installation methods
• Platforms and integrations
• VS Code integration
• Claude Code Desktop
• Claude Code on the web
• Claude Code in Slack
• GitHub Actions integration
• GitLab CI/CD integration
• Enterprise deployment overview