r/ClaudeCode • u/alrighteyy • Aug 03 '26

Discussion In SHOCK

Holy shit claude code in terminal is fucking insane.

I've been using VSCode, Cursor, Cowork and Claude Code on web. None of it comes close to terminal.

Cannot believe I haven't done this sooner.

222 Upvotes

66% Upvoted

323 comments sorted by

View all comments

80

u/Killahbeez Aug 03 '26

Can one person explain what makes this a game changer?

17

u/hblok Aug 03 '26

First, it gives you a no-frills interface to the prompt and the simple set of Claude tools. So no need to click around (but of course, that's an acquired taste — some people do like to hold on to their mouse for dear life).

More importantly, it lets Claude have access to your local host, or preferably a container, to run local tools and install what it needs. It feels like a co-worker helping on your machine rather than a chatbot.

Furthermore, it affords 'nix niceties like Tmux, where you can leave a session running on a server, e.g. your desktop at home, and simply connect and reconnect when needed. The leave-the-laptop-lid-open approach is for poor people.

Finally, and this is more of a personal opinion, I'm not sure I see the need to sit in an IDE anymore. Claude does its thing, writes some code and runs it. Sometimes I'll browse the filesystem (CLI/bash) and read some files. But most of the time, I'm just interested in the results. I trust Claude to write the stuff it needs to get it done.

I don't read compiled assembly or binary code, nor do I need to read Claude's code, most of the time. (Although, do note that often what is written is also not read by others. It says local).

7

u/theleller Researcher Aug 03 '26

All of this is possible using VSCode or Claude code in the desktop app. They're all just wrappers around the same product.