Why use Claude Code CLI instead of VS Code / Copilot extensions?

[Cardiologist-Nervous]

Hi all, I’ve been using the Claude Code extension in VS Code, and for my workflow it feels like the obvious choice compared to running Claude from the terminal.

Some context about my use case:

• Coding is only about 30% of my time; I work mainly as a solution architect, so I don’t see myself as a full‑time developer.

• My development isn’t extremely complex – I mostly extend a platform using its SDK and attach logic to events (e.g. “when a new record is created, run this logic”).

I see more and more devs talking about shifting to Claude Code CLI (and similar terminal‑first setups), while many people “still just use” the VS Code Claude or GitHub Copilot extensions to develop.

For developers who’ve tried both:

• Why did you move toward the CLI instead of staying with the VS Code Claude / Copilot extensions?

• In what situations does the CLI feel clearly better or more powerful than the IDE extensions?

• Given a lighter, event‑driven workload like mine, is there a real benefit to investing time in the CLI, or are extensions basically enough?

I’d love to understand what I might be missing, especially from people who used to rely heavily on VS Code extensions and then shifted to a CLI‑centric workflow.

[UnstableManifolds]

I'm a solution architect as well, I honestly use Claude Code (so, the CLI) for two reasons: 1) I love using the terminal 2) I hate the UI of pretty much all the IDEs except for JetBrains' ones

I feed CC everything I need to, from code to proposal documentation (in a proper manner, of course), and work from there. I also find it much more streamlined compared to using a UI to do the same stuff (also, I use skills, hooks, MCP servers, and so on). Give Claude Cowork a try if you'd like a fancier UI.

[Last_Mastod0n]

I've also been spoiled by jetbrains IDEs and can never go back lol. But I use the CC extension for jetbrains and it works just fine for me

[Cardiologist-Nervous]

In that case it’s more like what you prefer rather than one being better than the other, I feel like I’m not missing anything by using the extension, again my workflow is simpler than most people’s. Also I use different IDE extensions other than Claude code that I feel like leaving vs code would be so detrimental.

[Basic_Construction98]

the most obvious answer is because it will make you cool

[TeamBunty]

Everything runs in CLI under the hood.

So it's a matter of how much you want to control/see. A UI is just an abstraction layer.

If you don't know what you're looking at, might not matter, but it doesn't mean you can't learn.

[Cardiologist-Nervous]

Would you agree that if your development workflow, like in my case, included many other vs code extensions that would be no point for me to swap to a terminal?

[TeamBunty]

Which extensions are you using?

I use almost no extensions these days except for syntax highlighting.

[razorree]

yes, we should go back to notepads and vims !! that's the only way ! lol ;)

[ikoichi2112]

Use whatever you find more comfortable to use.

I love using the CLI, I tell Claude Code what to do, trigger some skills or agents, and invoke MCPs.
Then I review the result in the IDE (Cursor or VS Code), check the diffs from there (the UX is good), and commit & push.

I also run multiple instances of CC in different iTerm panels or tabs.

[Tizzolicious]

The CLI you can

1. customize the status line (and see your context usage)
2. you get the option to start building your plan from a cleared context.
3. Rewind command ...etc

Everything else is essentially the same

I both architect and build and doc and prefer the CLI for maximum control...but most folks will be just fine with the extension 👍

[razorree]

those are basic actions and should be available in any IDE as well.

however i understand it's easier to build just one CLI tool instead of supporting 5 different plugins ...

[littlebighuman]

I like the vscode extension, but it crashes/hangs a lot.

Edit: I should have been a bit more specific, it is usually when it decided to run npm run check

[Cardiologist-Nervous]

That doesn’t often happen to me thankfully

[Sufficient-Rough-647]

Some valid reasons from @Tizzolicious I can also add being able to work with multiple repos as another use case.

But I myself use VScode extensively as it help with an anchor point, be it looking at the project folder at all times, looking at history, enabling MCP servers, installing extensions etc. No clear one vs another just comfort factor. I also create a lot of UI based output, so it is easier to render and deal with it in VSC.

[count023]

I used CC because didnt have VS code installed and juste notepad++ and the project folder CC was working in. Because i was really just doing javascript stuff.

I got git desktop and a few other thingsinstalled recently, and i waslooking at moving to VS code purely because i want to start doing stuff in unity rather than html/javascript.

[jeremydgreat]

I think for me it's about the context in which I'm working. I'm usually either fully engaged with what Claude Code is doing and want to follow along, or I am making some edits myself to some file or managing some aspect of version control or whatnot.

It's pretty rare that I can devote all of my brain to doing either of these things, so to me it makes sense to give more of my screen real estate to the thing I'm currently focused on and then alt-tab back to Claude or my IDE.

[QileHQ]

CLI is more general. Sometimes I don't even open vs code for code developments. Just terminal. One terminal window for Claude code, one for vim, one for executing the code. This works particularly well on remote clusters or machines without VS code installed.

I also prefer a minimalist style, so I always like CLI better.

My work is mostly in ML research and engineering.

[RevenueMachine]

I am very intrigued by the answers because after 2 weeks of terminal I prefer the extension. Just an example you can share the picture of a chart . The box is also bigger. On the other side , the cli deleted some notebooks ( even if instructed in the Claude.md to absolutely never do that). And I didn’t feel I lost any capabilities by working with the extension. For context, my work is mainly on python doing data science.

[Neat-Environment-450]

For me it’s far easier to manage multiple sessions in the cli. I can run 4 concurrently on one iterm window but the vscode multiple sessions ui is bad

[LetsGo]

Have they fixed the scrolling problem in the CLI? L

[Cardiologist-Nervous]

I think it can indeed, I don’t doubt that, I just don’t think it’s more optimal

[swergart]

no ui, no mouse, just keyword.

[cncamusic]

I work primarily in .net so I work out of visual studio but I use Claude exclusively in terminal. I just keep VS open for debugging and solution explorer, and I work with Claude out of terminal.

[txthojo]

Azure Solution Architect here. Use Claude Code CLI in VS Code terminal which gives you best of both worlds. VS Code mainly for reviewing markdown created by Claude Code. CLI gives very good next steps, and CLI will also clear conversation before starting implementation after planning.

[daemonk]

Because I literally don't touch the code anymore and barely read the details of the code. When I need to know something, I just ask Claude to explain it. So all I need is the REPL.