logoalt Hacker News

0xffff2yesterday at 7:09 PM2 repliesview on HN

I'm curious about the opposite: Why would anyone use the CLI when, at least with Copilot, the VSCode plugin is super tightly integrated with VSCode, meaning the agent can see everything I can see. There's no mismatch in linter calls where I can see a lint in the ide that the agent can't find for example. I've had this problem even using CC in their VSCode extension, so I can't imagine it's not an issue in the CLI as well.

What's actually better in the CLI?


Replies

sz4kertoyesterday at 7:57 PM

We need sandboxing for any agent, so we run it within Docker - so we use CLI.

show 1 reply
nltoday at 2:13 AM

I use the Claude Code VSCode plugin for 80% of my work.

I prefer it because I can look at the code (although not as often anymore) and config (very often!) easily.

It also lets me jump to previous conversations easily.

There are a few cases where the CLI makes sense. One big one is if you are running multiple simultaneous sessions on a remote server using Tmux to have them preconfigured when you reconnect is nice.

Bun in general I don't see the benefit either.

show 1 reply