Home › Sources › Platforms and integrations

Platforms and integrations

Tags

official-docs claude-code-cli

Content

Documentation Index

Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt Use this file to discover all available pages before exploring further.

Platforms and integrations

Choose where to run Claude Code and what to connect it to. Compare the CLI, Desktop, VS Code, JetBrains, web, mobile, and integrations like Chrome, Slack, and CI/CD.

Claude Code runs the same underlying engine everywhere, but each surface is tuned for a different way of working. This page helps you pick the right platform for your workflow and connect the tools you already use.

Where to run Claude Code

Choose a platform based on how you like to work and where your project lives.

Platform Best for What you get
CLI Terminal workflows, scripting, remote servers Full feature set, Agent SDK, computer use on macOS (Pro and Max), third-party providers
Desktop Visual review, parallel sessions, managed setup Diff viewer, app preview, computer use and Dispatch on Pro and Max
VS Code Working inside VS Code without switching to a terminal Inline diffs, integrated terminal, file context
JetBrains Working inside IntelliJ, PyCharm, WebStorm, or other JetBrains IDEs Diff viewer, selection sharing, terminal session
Web Long-running tasks that don't need much steering, or work that should continue when you're offline Anthropic-managed cloud, continues after you disconnect
Mobile Starting and monitoring tasks while away from your computer Cloud sessions from the Claude app for iOS and Android, Remote Control for local sessions, Dispatch to Desktop on Pro and Max

The CLI is the most complete surface for terminal-native work: scripting, third-party providers, and the Agent SDK are CLI-only. Desktop and the IDE extensions trade some CLI-only features for visual review and tighter editor integration. The web runs in Anthropic's cloud, so tasks keep going after you disconnect. Mobile is a thin client into those same cloud sessions or into a local session via Remote Control, and can send tasks to Desktop with Dispatch.

You can mix surfaces on the same project. Configuration, project memory, and MCP servers are shared across the local surfaces.

Connect your tools

Integrations let Claude work with services outside your codebase.

Integration What it does Use it for
Chrome Controls your browser with your logged-in sessions Testing web apps, filling forms, automating sites without an API
GitHub Actions Runs Claude in your CI pipeline Automated PR reviews, issue triage, scheduled maintenance
GitLab CI/CD Same as GitHub Actions for GitLab CI-driven automation on GitLab
Code Review Reviews every PR automatically Catching bugs before human review
Slack Responds to @Claude mentions in your channels Turning bug reports into pull requests from team chat

For integrations not listed here, MCP servers and connectors let you connect almost anything: Linear, Notion, Google Drive, or your own internal APIs.

Work when you are away from your terminal

Claude Code offers several ways to work when you're not at your terminal. They differ in what triggers the work, where Claude runs, and how much you need to set up.

Trigger Claude runs on Setup Best for
Dispatch Message a task from the Claude mobile app Your machine (Desktop) Pair the mobile app with Desktop Delegating work while you're away, minimal setup
Remote Control Drive a running session from claude.ai/code or the Claude mobile app Your machine (CLI or VS Code) Run claude remote-control Steering in-progress work from another device
Channels Push events from a chat app like Telegram or Discord, or your own server Your machine (CLI) Install a channel plugin or build your own Reacting to external events like CI failures or chat messages
Slack Mention @Claude in a team channel Anthropic cloud Install the Slack app with Claude Code on the web enabled PRs and reviews from team chat
Scheduled tasks Set a schedule CLI, Desktop, or cloud Pick a frequency Recurring automation like daily reviews

If you're not sure where to start, install the CLI and run it in a project directory. If you'd rather not use a terminal, Desktop gives you the same engine with a graphical interface.

Platforms

Integrations

Remote access