I run a marketing agency, not an engineering team. So when people kept telling me to try Claude Code inside VS Code, my honest first reaction was: that’s a developer thing, not a me thing.
Then I spent a month using it to ship changes to our own site, draft technical docs, and untangle a few problems I’d normally have handed off. It turned out to be far more useful to a non-engineer than I expected — and also a bit more frustrating in places no one warns you about.
Here’s what actually happened.
What is Claude Code in VS Code?
Claude Code is Anthropic’s coding agent. Most people first meet it as a command-line tool, but it also runs as an extension directly inside VS Code (and JetBrains editors). Once installed, it lives in a side panel next to your files, reads your project, and can edit code, run commands, and explain what it’s doing as it goes.
The difference from a normal chat window is that it’s in your editor. It sees the files you have open, the structure of the repo, and the changes it makes show up as diffs you approve or reject. You’re not copying snippets back and forth — you’re watching an agent work in the same place you do.
Setting it up
Setup was genuinely quick. You install the extension from the VS Code marketplace, sign in with your Claude account, and a panel appears on the side. There’s no real configuration to wrestle with before you can ask it something.
A few things that helped me early on:
- Open the actual project folder, not a single file. Claude is far more useful when it can see the whole repo.
- Let it propose, then review the diff. Every edit shows up as a before/after you can accept or throw away. I never once let it change files blindly.
- Tell it your constraints up front. “Don’t touch the config files” or “match the existing style” saved me a lot of cleanup.
If you’ve ever installed a linter or a Git extension, this is no harder than that.
What it does well
It reads context instead of guessing
The thing that won me over is that it doesn’t treat your question in isolation. Ask it to “add a new blog post in the same format as the others” and it goes and looks at the others first — the frontmatter, the folder, the naming — then matches them. That’s the part that feels different from pasting code into a chatbot.
The diff workflow keeps you in control
I was nervous about an AI editing my files. The diff-by-diff approval removed most of that fear. Nothing changes until I say so, and I can read exactly what it’s about to do. For someone who isn’t a confident coder, that safety net matters more than raw speed.
It explains its reasoning
When it hit something it wasn’t sure about, it told me — and asked. That’s rare and welcome. I’d rather an agent pause and check than confidently break something.
It’s surprisingly good for non-code tasks
I used it to clean up markdown, rewrite documentation, find every place a broken link appeared across a folder, and tidy up messy data files. None of that is “programming” exactly, but it’s the kind of fiddly work that eats an afternoon. Having it in the editor where the files already live made it faster than any standalone tool.
Where it struggles
It’s not magic, and pretending otherwise does no one any favours.
- It can be overconfident on large, vague requests. Ask for something sprawling and underspecified, and it’ll happily make a dozen changes you didn’t quite want. Smaller, clearer asks get far better results.
- You still need to review everything. On a couple of occasions it “fixed” something that wasn’t broken. The diff view caught it, but only because I read it.
- Cost adds up if you let it run wild. Tight, scoped prompts aren’t just better quality — they’re cheaper.
- It’s not a substitute for understanding your own project. It accelerates someone who knows roughly what they want. It won’t rescue you if you have no idea what should happen.
Who it’s actually for
If you write code for a living, this is an easy yes — it removes a lot of grunt work and keeps you in your editor.
But the more interesting audience, to me, is people like marketers, founders, and operators who maintain a site or some technical content but aren’t full-time engineers. If you’ve ever stared at a repo wishing someone could just make a small change for you, this is close to that. You stay in control, you review every edit, and you learn a little about your own project in the process.
My verdict
After a month, Claude Code in VS Code earned a permanent spot in my workflow — with one rule: keep the requests small and specific, and read every diff.
It’s not a replacement for knowing what you’re doing. It’s a very capable assistant that does the careful, tedious parts faster, as long as you stay the one making the decisions. For a non-engineer who ships real changes, that turned out to be exactly the right trade.
If you’ve been on the fence because it sounds like a developer-only tool, I’d say try it on one small, real task. That’s how it won me over.
