Where to use Claude Code

Claude Code is available on multiple surfaces. The same underlying engine powers all of them — your CLAUDE.md files, settings and MCP servers work across all surfaces.

**Terminal** → full CLI, edits files, runs any command

**VS Code / Cursor** → inline diffs, @file mentions, conversation history in the editor

**JetBrains** → IntelliJ, PyCharm, WebStorm — interactive diff view

**Desktop App** → parallel sessions with Git isolation, visual review

**Web (claude.ai/code)** → no install, ideal for long background tasks

**GitHub Actions / GitLab CI** → automated PR review

**Slack** → mention @Claude with a bug report, get a PR back

**Chrome** → live web app debugging

1# Terminal — full power
2claude "fix the auth bug and run tests"
3
4# VS Code — open the Claude panel
5# Cmd+Shift+P → "Claude Code: Open"
6# Type: @src/auth/login.ts explain this
7
8# Web — long background tasks
9# Open claude.ai/code → start task → close tab → come back later
10
11# CI/CD — headless automation
12claude -p "review this PR for security issues"

1# Switching between surfaces mid-task:
2/teleport    # web session → local terminal
3/desktop     # terminal → Desktop App
4claude remote-control  # access terminal from phone/tablet

**Common pitfall:** Don't jump between surfaces for the same task. Start in one surface and stay there unless you have a specific reason to transfer (e.g., mobile review). Session state transfers cleanly but context may be lost.

Terminal is the most powerful surface — full CLI access, all commands, pipe support. Use VS Code for inline diff review. Use Web for long background tasks. You can always switch mid-session.

Install the Claude Code extension in VS Code now. Search for "Claude Code" in the Extensions marketplace (Cmd+Shift+X). Then try the same prompt in both Terminal and VS Code to compare.

Which surface gives you the most control and power with Claude Code?