IDE, web, CLI: choose the right environment Claude Code

Claude Code exists in five forms: CLI on the terminal, desktop app (Mac/Windows), web app on claude.ai/code, extension for VS Code, and extension for JetBrains. There are different interfaces on the same underlying model, but they optimize different workflows. Choosing poorly costs free friction; choosing well makes work smooth.

Independence Disclaimer: I am not affiliated with Anthropic. On my portfolio, I primarily use CLI (for the GSD workflow) + VS Code extension (for inline editing). The web app and desktop are secondary setups.

The five forms briefly

• Command Line InterfaceTerminal-native. Full file system access. MCP stdio native. Slash command + skill + GSD workflow structured. Excellent for batch workflow and automation.
• Desktop applicationGUI standalone Mac/Windows. Full file system access. MCP support. A more user-friendly UX than CLI for those who do not live at the terminal.
• Web application (Claude AI/Code)cloud-only, no setup locale. Project mode with custom instructions persistent. MCP support limited (no stdio, only HTTP remote). Good for chat and drafting.
• Visual Studio Code extensionInline editor integration. Pair programming during coding. CLI underneath for MCP+skill. Good for localized guided modifications.
• JetBrains pluginSimilar to VS Code, for IntelliJ / WebStorm / PyCharm. Analogous pattern.

Decision matrix for scenario

Mixed setup recommended

On my portfolio I use this setup:

1. Command Line Interface as primaryAll workflows GSD/gsd-plan-phase, /gsd-execute-phaseCustom skill for MCP sub-agent.
2. Visual Studio Code extension as a secondaryDuring coding manual (review post-execute, refactor viewed, debug). The extension uses the CLI underneath, so MCP + skills remain available.
3. Web application for a quick checkWhen I have a fast question not tied to the specific project ("tell me how it works with X pattern in language Y"). Zero setup overhead.

Desktop app and JetBrains: I don't use them. There's no gap that fills my setup. They're valid for other profiles (Java/Kotlin developers who live in IntelliJ find the JetBrains extension more fluid).

MCP differences

• Command Line Interface / Desktopstdio MCP native (server as local subprocess). Full ecosystem.
• Visual Studio Code / JetBrains extensionStandard input is coming from MCP via CLI beneath. It works but configuration goes to CLI level.
• Web applicationOnly HTTP remote MCP. No standard input. Drastically limits available ecosystem.

For heavy workflows with MCP (on my portfolio I use 8 MCP servers), CLI is the only reasonable choice.

File system access differences

• Command Line Interface / Desktop Integrated Development Environment extensionFull file system like the user who launches it. Read/write without additional permissions.
• Web applicationOnly files explicitly uploaded to the session are allowed. No access to local file system.

For code repository workflows on the web, it is limited. For drafting or general questions, it's fine.

I don't see any Italian text provided. Please provide the Italian text you'd like me to translate, and I'll be happy to assist you.

API call: same price cross-environment. The monthly invoice does not change if you use CLI vs web vs IDE ext: it depends on the consumed tokens, not from the interface.

Subscription Claude Pro (~€20/mo) includes access to all forms. No sub-pricing for CLI vs ext.

User Experience latency

Practical differences in UX latency:

• CLI: startup ~200ms, response streaming immediately.
• Desktop: starts up in about 1 second, with immediate response and continuous streaming.
• Web: startup browser tab (variable), immediate response streaming post-prompt.
• Integration overhead of approximately 500ms to 1 second per round trip.

Small differences, but cumulative on intense sessions. For workflows that require 50+ prompts per session, CLI wins in throughput.

Hybrid workflow typical (real day)

1. Morning: Sei pronto a iniziare la giornata con una bella colazione? XPHX0XPHX Se hai bisogno di aiuto, non esitare a contattarci al numero XPHX1XPHX. Il nostro team è sempre disponibile per fornirti assistenza e risolvere eventuali problemi. Speriamo che la tua giornata sia piena di successi e soddisfazione! Cordiali saluti, La tua azienda XPHX0XPHX tmux With Claude Code CLI and terminal repository, launch /gsd-execute-phase for Wave 2 in the background.
2. While Wave 2 is running: I open VS Code, during manual coding I use an extension for inline queries (rename refactor, fix typo).
3. Lunch: Pranzo: * *Pranzo*: claude.ai On your phone to read a thread of tech docs not attached to the project.
4. Afternoon: I'm going back to CLI for a review and plan-checker iteration 2 and a batch commit.

Three environments in a day, each for the right use case. Zero friction of switching because each is optimized for that specific micro-workflow.

Forcing an environment for every little thing

Forcing the CLI for everything: even for fast chats requires opening the terminal, navigating the path, waiting for startup. Pointless overhead for a throwaway query.

Forcing a web for everything: zero file system access = you must always copy-paste code. Enormous overhead for workflows on repositories.

Clean mix: choose an environment based on the task, not your preference.

What I learned writing this article

The thing I realized is that The choice of environment is a micro-decision you make 50 times a dayDon't think about it explicitly; opening CLI versus opening web versus clicking on extension vs code = choices made automatically. If you do well, accumulate minutes saved. If you do poorly, accumulate friction.

According to insight: my usage has stabilized at 3 environments after initial experimentation (also with desktop + JetBrains). For other professional profiles (e.g. Java/Kotlin in IntelliJ) the distribution would be different. There is no "universal setup" - there is the right setup for your workflow.

Avoided pattern

• Mono-environmentDiversity in the work kit pays.
• Open a chat window in the Command Line Interface (CLI) for a throwaway session.The web has zero startup cost, it's free.

A story worth sharing

Placeholder Section Original hybrid setups are welcome federico@federicocalo.dev.

Previous cluster: Hooks system Next cluster: Cost optimization →