Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Claude Code gets native LSP support

github.com

Post reply on HN
Print view View original

211–220 of 352 posts

Re: Claude Code gets native LSP support

#211

Post by rane »

odie5533 wrote: post #149
rane wrote: post #142

Earlier quoted context omitted.

You don't want to run tests after every file change, because that will distract Claude from finishing whatever it's doing and add noise to the context window. Of course the tests will be broken if Claude hasn't finished the full change yet. Running tests makes most sense on the Stop hook event, but personally I've found CLAUDE.md instruction of "Run `just check` after changes" to be effective enough. The Stop hook ha…

Won't the LSP distract Claude too? I am trying to think of ways to make Claude faster at iterating by reducing tool calls. That always seems to be a bottleneck when it's doing tons of back-and-forth with tool calls.

Depends on Anthropic has implemented it I guess. I haven't had it activate yet despite the prompt to install an LSP.

Re: Claude Code gets native LSP support

#212

Post by imiric »

losvedir wrote: post #196
imiric wrote: post #104

Earlier quoted context omitted.

I don't understand. You're highlighting a project that implements an "agent" as a counterargument to my claim that the bulk of improvements are from "agents"? Sure, the models themselves have improved, but not by the same margins from a couple of years ago. E.g. the jump from GPT-3 to GPT-4 was far greater than the jump from GPT-4 to GPT-5. Currently we're seeing moderate improvements between each release, with "agen…

They're pointing out that the "agent" is just 100 lines of code with a single tool. That means the model itself has improved, since such a bare bones agent is little more than invoking the model in a loop.

That doesn't make sense, considering that the idea of an "agentic workflow" is essentially to invoke the model in a loop. It could probably be done in much less than 100 lines.

This doesn't refute the fact that this simple idea can be very useful. Especially since the utility doesn't come from invoking the model in a loop, but from integrating it with external tools and APIs, all of which requires much more code.

We've known for a long time that feeding the model with high quality contextual data can improve its performance. This is essentially what "reasoning" is. So it's no surprise that doing that repeatedly from external and accurate sources would do the same thing.

In order to back up GP's claim, they should compare models from a few years ago with modern non-reasoning models in a non-agentic workflow. Which, again, I'm not saying they haven't improved, but that the improvements have been much more marginal than before. It's surprising how many discussions derail because the person chose to argue against a point that wasn't being made.

Re: Claude Code gets native LSP support

#213

Post by rurban »

spullara wrote: post #31

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…

Just customize emacs. Their refactoring and AI packages are good, and it's faster.

Re: Claude Code gets native LSP support

#214

Post by marwamc »

spullara wrote: post #97
dist-epoch wrote: post #73

Earlier quoted context omitted.

People keep saying how amazing IntelliJ is at refactoring, but then you realize the talk about "rename thing" and "extract function". This is 5% of what refactoring is, the rest is big scale re-architecting code where these tools are useless. The agents can do this big scale architecturing if you describe exactly what you want. IntelliJ has no moat here, because they can do well 5% of what refactoring is.

I think that the commonly used refactoring functions would make a big difference and right now most IDEs are pretty bad at them (especially across all the languages jetbrains supports): - rename variable/function - extract variable/function - find duplicate code - add/remove/extract function parameter - inline a function - moving code between classes - auto imports Others are used more rarely and can probably be left…

Agentic refactoring was such a chore I ended up building this for my refactoring workflows.

https://gitlab.com/rhobimd-oss/shebe/-/blob/main/docs/guides...

https://gitlab.com/rhobimd-oss/shebe/-/tree/main?ref_type=he...

Then in skills or CLAUDE.md I instruct claude to use this mcp tool to enumerate all files need changing/updating.

Re: Claude Code gets native LSP support

#215

Post by oblio »

csomar wrote: post #198
remus wrote: post #126

Earlier quoted context omitted.

In a similar vein, I really struggle to understand why copilot is so crap when writing SQL and I'm connected to the database. The database has so much context (schema names, column names, constraints etc.) yet copilot regularly hallucinates the most basic stuff like table and column names, which standard auto complete has managed fine for the last 20+ years.

No one is interested to solve hard problems. The broad industry got lucky with LLMs and everyone is now blindly burning capital at this. If you think they can't be that stupid remember the covid super hiring frenzy.

Heh, read The Big Short. A large point of the book is that a lot of rich people are both greedy (which we already assumed) and also stupid (which we didn't assume).

Re: Claude Code gets native LSP support

#216

Post by cherryteastain »

kachapopopow wrote: post #197
spullara wrote: post #31

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 am trying my damn hardest to drop jetbrains, the only thing they have a stronglehold over is their amazing rust analyzer in rustrover. And yah I agree that they are dropping the ball on providing actual intellisense to AI tools, like why not? It's probably less than 10 lines of code.

What does rustrover do that rust-analyzer itself cannot?

Re: Claude Code gets native LSP support

#217

Post by jameslk »

NitpickLawyer wrote: post #67
frays wrote: post #54

Earlier quoted context omitted.

Interesting to see that you work at OpenAI but had to build a skill like this yourself. Surprised that you don't have internal tools or skills that could do this already! Shows how much more work there is still to be done in this space.

> Shows how much more work there is still to be done in this space. This is why I roll my eyes every time I read doomer content that mentions an AI bubble followed by an AI winter. Even if (and objectively there's 0 chance of this happening anytime soon) everyone stops developing models tomorrow , we'll still have 5+ years of finding out how to extract every bit of value from the current models.

Useful technology can still create a bubble. The internet is useful but the dotcom bubble still occurred. There’s expectations around how much the invested capital will see a return and growing opportunity cost if it doesn’t, and that’s what creates concerns about a bubble. If a bubble bursts, the capital will go elsewhere, and then you’ll have an “AI winter” once again

Re: Claude Code gets native LSP support

#218

Post by gizzlon »

_virtu wrote: post #175
conradfr wrote: post #130

Earlier quoted context omitted.

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...

The commit workflow was what kept me locked in to the ecosystem for so long. LazyGit was so good that it convinced me I didn’t need JetBrains anymore. If you love the workflow with JB for commits check out LazyGit. It’s a TUI so you can use it in any editor without much friction.

Just found LazyGit as well. it's amazing!

Also like Sublime Merge, if you want a GUI (paid though)

Re: Claude Code gets native LSP support

#219

Post by kachapopopow »

cherryteastain wrote: post #216
kachapopopow wrote: post #197

Earlier quoted context omitted.

I am trying my damn hardest to drop jetbrains, the only thing they have a stronglehold over is their amazing rust analyzer in rustrover. And yah I agree that they are dropping the ball on providing actual intellisense to AI tools, like why not? It's probably less than 10 lines of code.

What does rustrover do that rust-analyzer itself cannot?

rust analyzer fails 13 lines into my main.rs file because I use something rust analyzer just doesn't work with that well, also it's much faster

Re: Claude Code gets native LSP support

#220

Post by ako »

JamesSwift wrote: post #39
CharlesW wrote: post #3

It's strangely difficult to find official information about this, but here's what I've learned: • Use `/plugin` to open Claude Code's plug-in manager • In the Discover tab, enter `lsp` in the search box • Use `spacebar` to enable the ones you want, then `i` to install Hope that helps!

Yeah, I posted here because I was completely blindsided when my claude asked if I wanted to install a go lsp. I didnt even know that was a thing. A little googling led to this changelog from 3 days ago, but I was surprised I hadnt seen any previous mentions of this online (from either creators, anthropic, or HN posts). I am disabling it for now since my flow is fine at the moment, I'll let others validate the usefuln…

I had a conversation with Claude code 2 weeks ago where it mentioned early support for LSP had been added into Claude code. Have been working on a LSP for a custom language since then.
Post reply on HN