Where to Use Claude Code — Desktop, Web, Terminal, and IDE

Claude Code is not a single app. It runs across half a dozen surfaces — from the terminal on your laptop to your phone screen. Each one connects to the same underlying AI, but the experience and trade-offs differ. This guide walks through every option so you can pick the right one for how you work.

1. The Terminal (CLI)

The terminal is where Claude Code started. If you are comfortable typing commands, this is the most direct and powerful way to use it.

Installing

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

claude

When to Use the Terminal

• Scripting and automation — pipe output, chain commands, integrate Claude into shell scripts
• Headless environments — SSH sessions, CI/CD pipelines, remote servers
• Maximum control — pass flags, set models, configure context explicitly

1# One-shot mode: ask a question without entering interactive mode
2claude -p "Explain the error in server.log"
3 
4# Pipe data directly into Claude
5cat data.csv | claude -p "Summarize this dataset"
6 
7# Start with a specific model
8claude --model opus

2. Desktop App

The desktop app gives you a standalone window for Claude Code without needing to open a terminal or editor. It is available for Mac and Windows.

Getting Started

When to Use the Desktop App

• You prefer a visual interface — file browser, clickable history, drag-and-drop
• You are not a developer — no terminal knowledge required
• Quick project work — open a folder, ask questions, get changes without setting up an editor

3. Web App (claude.ai/code)

The web app runs entirely in your browser. No downloads, no installs — just open claude.ai/code and start working.

What It Can Do

• Write, refactor, and explain code in a conversation
• Generate files you can download
• Run in any browser on any machine (Chromebook, library computer, a friend's laptop)

What It Cannot Do (Without Help)

The web app does not have direct access to your local file system. It cannot read your project files, run terminal commands, or execute tests on its own.

There is a workaround: Remote Control. When you pair the web app with a desktop instance of Claude Code, the web interface can send instructions that execute on your local machine. More on this in the Mobile section below.

When to Use the Web App

• Away from your dev machine — quick tasks from any browser
• Exploring ideas — brainstorming, pseudocode, architecture discussions
• Sharing sessions — easy to share a conversation link with a collaborator

4. VS Code Extension

If you write code in VS Code, the Claude Code extension puts the AI right inside your editor. No context switching, no copy-pasting between windows.

Installing

Key Features in VS Code

• Inline diffs — Claude's proposed changes appear as a diff right in the editor. Accept or reject each change individually.
• Selection context — highlight a block of code, then ask Claude about it. The selection is automatically included as context.
• Terminal integration — Claude can run commands in VS Code's built-in terminal.
• Workspace awareness — the extension reads your project files, CLAUDE.md, and .gitignore to understand the project structure.

# Example: select a function, then type in the Claude panel
"Add error handling and unit tests for this function"

5. JetBrains Plugin

If you use IntelliJ IDEA, PyCharm, WebStorm, GoLand, or any other JetBrains IDE, Claude Code works there too.

Installing

Key Features in JetBrains

• Diff viewer integration — proposed changes show up in the familiar JetBrains diff tool
• Project-wide context — Claude reads your project structure, dependencies, and run configurations
• Same keyboard shortcuts — ⌘/Ctrl + Esc works across all JetBrains IDEs

6. Mobile (iOS / Android)

You can interact with Claude Code from your phone using the Remote Control feature. You are not running Claude locally on your phone — instead, you send instructions from the Claude mobile app, and Claude executes them on your desktop machine.

How It Works

When to Use Mobile

• Monitoring a long-running task — check on a build or migration from the couch
• Quick fixes on the go — "Fix the typo in the homepage hero text and deploy"
• Voice-driven development — dictate instructions while walking or commuting

For a deep dive on Remote Control setup and Voice Mode, see Voice Mode and Remote Control.

Choosing the Right Surface

Here is a quick comparison to help you decide where to start.

Not Sure Where to Start?

Follow this decision tree:

• Never used a terminal before? Start with the Desktop App. It gives you full Claude Code power with a friendly interface.
• Already use VS Code? Install the VS Code extension. You will barely notice the transition.
• Already use a JetBrains IDE? Install the JetBrains plugin. Same idea.
• Comfortable with the command line? The Terminal CLI gives you the most flexibility.
• Just want to try it right now? Open the Web App — zero setup, instant access.

What They All Share

Regardless of which surface you pick, the core experience is the same:

• Same AI model — Claude Opus, Sonnet, or Haiku, depending on your plan and preference
• Same context system — CLAUDE.md files, .gitignore awareness, project memory
• Same tool access — MCP servers, file editing, terminal commands (where the surface supports it)
• Same conversation model — ask follow-ups, refine instructions, iterate on results

The surface you choose is about ergonomics, not capability. Pick the one that fits your existing workflow, and switch when the situation calls for it.

Next Steps

• Ready to install? Follow the macOS Setup Guide or Windows Setup Guide for a complete walkthrough.
• Already set up? Learn the difference between Claude Code and the web chat interface.