IDEs have LSP support because they have a plugin that connects to an LSP server. The plugin is a very small piece of code compared to the language server. Creating a new client is not reinventing the wheel. In fact the entire philosophy of LSP is: one server to many different clients.

CLIs can also have a small piece of code that connects to an LSP server. I don’t see why IDEs should be the sole beneficiary of LSP just because they were the first clients imagined by the LSP creators.

I have not yet had an IDE-based agent give anything close to the CLI Claude Code experience.

So until it manages to do that, I’ll keep being bullish on what works.

Google Antigravity is pretty much close to Claude Code imo

Including the Claude Code v2 experience in VSCode.

Thank you, whoever added the setting to revert back to the terminal experience.

nothing about that is because its a cli app

I just saw a video of non-technical person describing how they use claude code to automate various workflows. They actually tried vscode and then the desktop gui.

Yet they preferred the CLI because it felt "more natural"

With agents, and Claude Code, we are *orchestrating* ... this is an unresolved UI/UX in industry. The same reasons `kubectl` didn't evolve to GUI probably apply here.

It's less about the codebase, more about the ability to conduct anything on the computer - you are closest to that in the terminal. https://backnotprop.com/blog/its-on-your-computer/

There are plenty of GUIs for managing kubernetes, from k9s to redhat's Openshift gui, rancher, Lens, etc

big reach

Curious if you have a link to that video. Im trying to bridge the gap of claude code to non technical users and am trying to consume all prior art.

This is also what I’ve been doing. I can’t find the exact video but this is another good example: https://www.tiktok.com/@thinkwithv/video/7580186972208024863

The comments are usually insightful. Even in that video the terminal ui is brought up and she mentions her preference.

What IDE agent gets access to LSP?

I use Zed and unless there is some MCP server that provides the same thing as the LSP server, the Zed agent won't have access, even though it's in an IDE that supposedly has this information

Cursor, Copilot, Roo Code, Cline, among others.

Hi, I just looked up and two weeks ago someone made this suggestion in Cursor forum

https://forum.cursor.com/t/support-of-lsp-language-server-pr...

> Feature request for product/service

>

> Cursor IDE

>

> Describe the request

>

> It would be a huge step up if agent could interact with LSP (Language Server Protocol).

>

> It would offer :

>

> renaming all instances of a symbol over all files in one action

> quick navigation through code : fast find of all references to a property or method

> organize imports, format code, etc…

And last Friday a Cursor engineer replied "Thanks for the idea!"

So how does the AI agent in Cursor currently have access to LSP?

(I am most interested in having the agent use LSP for type checking, documentation of a method call, etc. rather than running slower commands)

(note, there is an open PR for Zed to pull LSP diagnostics into an AI agent thread https://github.com/zed-industries/zed/pull/42270 but it would be better if agents could make arbitrary LSP queries or something like that)

Cursor Agent can get diagnostics as far as I'm aware. Using LSP for renaming and stuff like that, I haven't seen yet.

Oh ok, thanks.

It would be so cool if LLMs could get the type of a variable when it's unclear (specially in languages with overloading and whatnot). Or could get autocomplete if they get stuck with a code. Really I think that agents and LSP should be hybrid, and maybe the agent could inform the LSP server of some things like things to warn (IDE diagnostics could be driven by a combination of LSP and AI agents)

cursor

Well my editor is in the terminal, so is my chatbot. I dont really want to change to an IDE to use a desktop app and a chatbot that both have half-baked UIs trying to complement each other.

For many of us, the plus of the CLI form factor is it doesn't tie us to a particular IDE.