r/ClaudeAI • u/BloodNext7144 • 5d ago
Question about Claude Code Claude Desktop (Code tab) vs CLI in VS Code
Hey all, quick question that turned into a friendly argument at work :/
I use Claude Desktops Code tab, with Obsidian for my notes. My boss says I should switch to the CLI in VS Code because it works better and uses WAY fewer tokens. I tried both and honestly didnt notice much difference.
What do you guys use, should I switch?
No need for a long reply. If you know of any research or tests on this just drop a link. I m genuinely curious
1
u/norviking 5d ago
Token use = context x turns. I dont know if VS code provides some sort of state management or support, then it is possible. Cli does not alone afaik. I get about -20% tokens with a system that does all of the state managmenet, planning and task instructions outside claude code or agents. Mostly from lower reads. Thats compared to auto compact at 300k context, so my system and vanilla claude both auto compacted to make it fair. If you use onw convo that auto compact when claude code wants near 1000k context you will spend waaaaaay more tokens. If you open many small new client chats, you will save some tokens, but it will be a confusing mess.
1
u/pietrzm 5d ago
You can use CLI in https://github.com/novadeck-org/novadeck. You get all the goodies of the desktop app while still running bare CLIs
1
u/clazman55555 5d ago
I don't use the CLI in VSCode, I use the more chat style mode. There are a few things that don't work due to the differences, mainly looking at workflows and subagents, some things related to MCPs and permission settings, but they can either be set in the config files or just code up a web browser to pull the info and display it.
1
u/EnvironmentalLeg8506 5d ago
I’d ask what the “WAY fewer tokens” comparison was based on. Same model, same task, same starting files, and fresh sessions on both sides? Without that, it’s hard to separate the interface from differences in what each session read or did.
If you want to test it, use two copies of the same small task and compare both the usage and the result. A run that reads less but misses a requirement isn’t necessarily more efficient. Also check whether both interfaces expose comparable usage figures before treating the numbers as equivalent.
Your trials feeling similar doesn’t prove they’re identical, but it is a reasonable reason not to switch solely on an unsubstantiated token claim. There may still be workflow reasons to prefer one.
0
u/Yedapo 5d ago
Since you tried both and didn't notice a difference, I'd lean toward staying put. In my experience token use comes mostly from how much context the session drags around, like a big CLAUDE.md, long chats, and huge file reads, not from which window you type in. If your boss wants numbers, a quick check is to run the same small task in a fresh session in each one and compare what /context or the usage readout says before and after. The one real reason to pick the CLI in VS Code is if you want the editor and terminal side by side, otherwise it's mostly preference.
1
u/usecornercase 5d ago
I don't know of a clean apples-to-apples benchmark. I wouldn't assume the CLI is cheaper by itself: token use follows the model and the context actually sent (repo instructions, files read, prior turns, tool output), and those can differ between interfaces. To test it, run the same task on the same repo with the same model and instructions several times, then compare the usage each client reports while noting retries and tool calls. If you're on a flat subscription, lower token counts may not change what you pay.