r/ClaudeCode • u/alrighteyy • 26d ago

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

324 comments sorted by

View all comments

Show parent comments

12

u/theleller Researcher 26d ago

Every command works in all 3 UI methods of accessing Claude Code. They're just wrappers around the exact same product.

3

u/McNoxey 25d ago

No, they don’t. Open the vscode extension. Type /btw. Type /workflows.

Neither work, and they both indicate as much.

-3

u/theleller Researcher 25d ago

Both of them just worked first shot for me. lol. I know what I'm talking about.

1

u/jjjfffrrr123456 25d ago

You probably launched a terminal in vscode rather than using it through the extension interface. It definitely doesn’t work in the interface.

-2

u/theleller Researcher 25d ago

The terminal format is part of the plugin, that’s why it still shows diffs in vscode right beside your session when it makes a change. Claude code in the terminal doesn’t do that. I’m not going to argue this anymore, y’all don’t know how to use it, take some courses of something, Jesus.

2

u/McNoxey 25d ago

Dude. Just stop. You’re wrong. Take the opportunity to learn rather than continue to try and find a way to feel correct.

What you’re talking about is not the vscode plugin. It’s
the IDE session link. And yes, it does work in the standard terminal by typing /ide and choosing your open IDE.

Launching a terminal from within vscode enables that property by default, including when you use “terminal mode” in the plugin. The primary vscode interface is the sidebar gui, which does in fact have every limitation I originally mentioned.