Skip to main content
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.
PlatformBest forWhat you get
CLITerminal workflows, scripting, remote serversFull feature set, Agent SDK, computer use on macOS (Pro and Max), third-party providers
DesktopVisual review, parallel sessions, managed setupDiff viewer, app preview, computer use and Dispatch on Pro and Max
VS CodeWorking inside VS Code without switching to a terminalInline diffs, integrated terminal, file context
JetBrainsWorking inside IntelliJ, PyCharm, WebStorm, or other JetBrains IDEsDiff viewer, selection sharing, terminal session
WebLong-running tasks that don’t need much steering, or work that should continue when you’re offlineAnthropic-managed cloud, continues after you disconnect
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. 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.
IntegrationWhat it doesUse it for
ChromeControls your browser with your logged-in sessionsTesting web apps, filling forms, automating sites without an API
GitHub ActionsRuns Claude in your CI pipelineAutomated PR reviews, issue triage, scheduled maintenance
GitLab CI/CDSame as GitHub Actions for GitLabCI-driven automation on GitLab
Code ReviewReviews every PR automaticallyCatching bugs before human review
SlackResponds to @Claude mentions in your channelsTurning 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.
TriggerClaude runs onSetupBest for
DispatchMessage a task from the Claude mobile appYour machine (Desktop)Pair the mobile app with DesktopDelegating work while you’re away, minimal setup
Remote ControlDrive a running session from claude.ai/code or the Claude mobile appYour machine (CLI or VS Code)Run claude remote-controlSteering in-progress work from another device
ChannelsPush events from a chat app like Telegram or Discord, or your own serverYour machine (CLI)Install a channel plugin or build your ownReacting to external events like CI failures or chat messages
SlackMention @Claude in a team channelAnthropic cloudInstall the Slack app with Claude Code on the web enabledPRs and reviews from team chat
Scheduled tasksSet a scheduleCLI, Desktop, or cloudPick a frequencyRecurring 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

  • CLI quickstart: install and run your first command in the terminal
  • Desktop: visual diff review, parallel sessions, computer use, and Dispatch
  • VS Code: the Claude Code extension inside your editor
  • JetBrains: the extension for IntelliJ, PyCharm, and other JetBrains IDEs
  • Claude Code on the web: cloud sessions that keep running when you disconnect

Integrations

  • Chrome: automate browser tasks with your logged-in sessions
  • Computer use: let Claude open apps and control your screen on macOS
  • GitHub Actions: run Claude in your CI pipeline
  • GitLab CI/CD: the same for GitLab
  • Code Review: automatic review on every pull request
  • Slack: send tasks from team chat, get PRs back

Remote access

  • Dispatch: message a task from your phone and it can spawn a Desktop session
  • Remote Control: drive a running session from your phone or browser
  • Channels: push events from chat apps or your own servers into a session
  • Scheduled tasks: run prompts on a recurring schedule