3 ms·

Why make it a vscode extension if the point of these 3 tools is a cli interface? Meaning most of the people I know use these tools without VSCode. Is VSC requir

by mlrtime 10mo ago

Why make it a vscode extension if the point of these 3 tools is a cli interface? Meaning most of the people I know use these tools without VSCode. Is VSC required?

bahaAbunojaim 10mo ago
That’s a great idea! I can make it a CLI too
KronisLV 10mo ago
> Meaning most of the people I know use these tools without VSCode. I guess it depends? You can usually count on Claude Code or Codex or Gemini CLI to support the model features the best, but sometimes having a consistent UI across all of them is also nice - be it another CLI tool like OpenCode (that was a bit buggy for me when it came to copying text), or maybe Cline/RooCode/KiloCode inside of VSC, so you don't also have to install a custom editor like Cursor but can use your pre-existing VSC setup. Okay, that was a bit of a run on sentence, but it's nice to be able to work on some context and then to switch between different models inline: "Hey Sonnet, please look at the work of the previous model up until this point and validate its findings about the cause of this bug." I'd also love it if I could hook up some of those models (especially what Cerebras Code offers) with autocomplete so I wouldn't need Copilot either, but most of the plugins that try to do that are pretty buggy or broken (e.g. Continue.dev). KiloCode also added autocomplete, but it doesn't seem to work with BYOK.
- bahaAbunojaim 10mo ago
  Very true, I like the fact that I can now use them with a consistent UI, shared context and ability to brainstorm Will definitely try to add those features in a future release as well
davidmurdoch 10mo ago
Huh. I know hundreds that use LLMs in a VSCode based IDE, and 3 that use the CLI.
- datameta 10mo ago
  I was a proponent initially of CLI when Claude integration with VSCode required a WSL instance, but now that it is integrated directly into VSCode I feel one grouping of tooling hiccups is now ruled out in my workflow. The only (major) nitpick I have is that it wont let you finish typing and cuts you off when asking whether/how to proceed.

by mlrtime 10mo ago

Why make it a vscode extension if the point of these 3 tools is a cli interface? Meaning most of the people I know use these tools without VSCode. Is VSC required?

bahaAbunojaim 10mo ago

That’s a great idea! I can make it a CLI too

KronisLV 10mo ago

> Meaning most of the people I know use these tools without VSCode. I guess it depends? You can usually count on Claude Code or Codex or Gemini CLI to support the model features the best, but sometimes having a consistent UI across all of them is also nice - be it another CLI tool like OpenCode (that was a bit buggy for me when it came to copying text), or maybe Cline/RooCode/KiloCode inside of VSC, so you don't also have to install a custom editor like Cursor but can use your pre-existing VSC setup. Okay, that was a bit of a run on sentence, but it's nice to be able to work on some context and then to switch between different models inline: "Hey Sonnet, please look at the work of the previous model up until this point and validate its findings about the cause of this bug." I'd also love it if I could hook up some of those models (especially what Cerebras Code offers) with autocomplete so I wouldn't need Copilot either, but most of the plugins that try to do that are pretty buggy or broken (e.g. Continue.dev). KiloCode also added autocomplete, but it doesn't seem to work with BYOK.

bahaAbunojaim 10mo ago
Very true, I like the fact that I can now use them with a consistent UI, shared context and ability to brainstorm Will definitely try to add those features in a future release as well

davidmurdoch 10mo ago

Huh. I know hundreds that use LLMs in a VSCode based IDE, and 3 that use the CLI.

datameta 10mo ago
I was a proponent initially of CLI when Claude integration with VSCode required a WSL instance, but now that it is integrated directly into VSCode I feel one grouping of tooling hiccups is now ruled out in my workflow. The only (major) nitpick I have is that it wont let you finish typing and cuts you off when asking whether/how to proceed.