Live data from Hacker News

Claude Code gets native LSP support

github.com

241–250 of 352 posts

Re: Claude Code gets native LSP support

#241

Earlier quoted context omitted.

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 navig…

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

Re: Claude Code gets native LSP support

#242

I hate everything about the Claude code plugin system. They saw GitHub Actions supply chain Fiasco and said: great let's add hallucinations on top. It's that bad. It's embarrassingly bad. No lock files. Nothing. And then most plugins in turn install MCPs from pypi with uvx so you have two layers of no pinning. It's a supply chain nightmare. It's so bad that I'm ashamed for our industry

Yeah uvx gets abused out of its convenience. uv has many useful features like dev dependencies and inline dependencies, that are much more reliable than uvx.

One tip for in-line dependencies: set a max date to lock your packages - reliable and simple for small scripts.

Re: Claude Code gets native LSP support

#243
post #241

Earlier quoted context omitted.

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 navig…

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)

Re: Claude Code gets native LSP support

#244

I really can't understand why JetBrains hasn't integrated its refactoring tools into the AI system. Really missed the boat on making their platform transformational for AI coding. Imagine how much smaller the context would be for a tool that renames a function than editing hundreds of files. This LSP support is a good start but without the mutation functions it is still pretty lackluster. Plus LSPs aren't as good as…

> I really can't understand why JetBrains hasn't integrated its refactoring tools into the AI system.

Because their refactoring tools are not a "slap on a couple of commands and delegate actual work to external code" like LSP? Because their tools are a huge collection of tools deeply integrated into the IDE? Including custom parsers, interpreters and analysers?

Re: Claude Code gets native LSP support

#245

Earlier quoted context omitted.

When you become complacent and your ego isn’t checked, you think you have the hottest thing. Hubris is hard. They had a pretty big moat that they let vscode eat away at. I don’t think they saw any of this coming and are struggling to make sense of it.

They are trying now to create an agent-first IDE. I think they are too big to move on this. https://blog.jetbrains.com/fleet/2025/12/the-future-of-fleet...

So many salty fools who bought into “professional|enterprise grade ide” cool aid. Glad to see upstarts eating their lunch, they’ve been complacent for far too long.

Re: Claude Code gets native LSP support

#246
post #202

Earlier quoted context omitted.

They've already done that. After the Junie fiasco, they pivoted to "AI Assistant", where Junie is just another provider alongside Anthropic and OpenAI. In theory, you have Claude Code inside Jetbrains IDEs now. What's incredible is just how bad it works. I nearly always work with projects that mount multiple folders, and the IDE's MCP doesn't support that. So it doesn't understand what folders are open and can't inte…

Yeah, it's quite odd that they can't get AI tools to work, especially considering so many OSS tools available that work surprisingly well (cline, opencode, etc.).

How do these compare? I'm very familiar with Augment and particularly enjoy its fast completions. I mostly don't use its agent, but rather Claude Code in the terminal, because the agent seems superior.

But Augment is not the most stable. I've had lots of serious problems with it. The newest problem that's pushing me over the edge is that it's recently have been causing the IDE to shoot up to use all cores (it's rare to see an app use 1,000% CPU in the macOS Activity Monitor, but it did it!) when it needs to recompute indexes, which is the only thing that has ever made my M2 Mac run its fan. It's not very reliable generally (e.g. autocompletions don't always appear), so I'd be interested in trying alternatives.

Re: Claude Code gets native LSP support

#247
What I've wondered about is whether there is a use in having an LLM that operates on AST symbols (or some IR representation) as input and/or output. It would be language specific of course (though maybe using something like MLIR is somewhat portable), but I would think it would result in a higher quality neural network, a reduction in tokens, etc.

Re: Claude Code gets native LSP support

#248
post #203

Earlier quoted context omitted.

Really? While there its certainly slightly annoying because they have the "double menu bar" if they use a non-standard one like the jetbrains ides do... I feel like wsl gui support has essentially become a "solved issue" for a while now.

Yes and no, GitKraken actually have a graphical interface for WSL (or Linux generally), but it is barely usable as the WSL-g does not really work well. It's blurry for Hi-Res screen and the performance is like hell. I would never try running any graphical stuff in WSL anymore, not worth it. VMWare with a graphical installation of any Linux system would be a preferred choice as I'm testing lately.

Or Proxmox or just virt-manager

Re: Claude Code gets native LSP support

#249
post #75

Earlier quoted context omitted.

They wanted to, but they’re still waiting for the IDE itself to simply load.

You joke and folks downvote, but this is my biggest issue with WebStorm. I'm seriously considering switching for the first time in 16 years. Zed is quite snappy. The Claude Code integration in VS Code is brilliant. I've used the CLI in the JetBrains terminal. I had no idea I could revisit past conversations until I used the VS Code extension!

Zed is snappy in the same way that notepad ++ is snappy: If you don't support 10% of language features you can avoid the hard work. Unfortunately this means that non trivial projects have false positive errors everywhere.

Re: Claude Code gets native LSP support

#250

I really can't understand why JetBrains hasn't integrated its refactoring tools into the AI system. Really missed the boat on making their platform transformational for AI coding. Imagine how much smaller the context would be for a tool that renames a function than editing hundreds of files. This LSP support is a good start but without the mutation functions it is still pretty lackluster. Plus LSPs aren't as good as…

Jetbrains seems a bit lost these days. Look at that very recent screw up [0]. I thought about moving after 10+ years when they abandoned the commit modal, and jacked up the plan prices, but I barely understand how to commit things in Vscode anyway. Let's see in 2026. [0] https://blog.jetbrains.com/datagrip/2025/12/18/query-console...

Did they abandon the commit modal? In 2024 line it's disabled by default (in favor of tool window) but you can enable it back.
Post reply on HN