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…
Claude Code gets native LSP support
291–300 of 352 posts
Re: Claude Code gets native LSP support
#292insane way to distribute a core product considering the state of npm.
Re: Claude Code gets native LSP support
#293I 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
its completely asinine to install npm globals these days, especially one that is such a juicy supply chain attack target
Re: Claude Code gets native LSP support
#294Re: Claude Code gets native LSP support
#295Earlier quoted context omitted.
Are you having a positive experience with Codex compared to Claude Code? Codex in my brief experience was... not good w/ 5.1
Just to provide another datapoint - tried codex September / October after seeing the glowing reviews here, and it was, all in all, a huge letdown. It seems to be very efficient context-wise, but at the same time made precise context-management much harder. Opus 4.5 is quite a magnificent improvement over Sonnet 4.5, in CC, though. Re tfa - I accidentally discovered the new lsp support 2 days ago on a side project in…
- Codex required around 30 passes on that loop, Claude did it in ~5-7.
- I thought Codex's was "prettier", but both were functional.
- I dug into Claude's result in more depth, and had to fix ~5-10 things.
- Codex I didn't dig into testing quite as deeply, but it seemed to need less fixing. Still not sure if that is because of a more superficial view.
- Still a work in progress, have not completed a full document signing workflow in either.Re: Claude Code gets native LSP support
#296Earlier quoted context omitted.
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.
I'm kinda reading this with disbelief. Are there people whose primary use case for IDE is... git gui?
Re: Claude Code gets native LSP support
#297Earlier quoted context omitted.
They already kinda did. They brough ACP support which allows you to somewhat integrate Claude Code, Gemini CLI or OpenCode they also recently brought BYOK support so you can use an existing provider and don't pay extra subscription for it.
ACP seems super under the radar. It has some support, but it got merged into A2A, which I don't hear anyone talking about, so it seems like it's going to die on the vine.
Re: Claude Code gets native LSP support
#298I 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...
Re: Claude Code gets native LSP support
#299I 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...
Re: Claude Code gets native LSP support
#300Earlier quoted context omitted.
You made me realize that I actually do use it, since I often look at git blame and the past changes. And I like the (recent?) update in which the changes from current commit (not only stage) are coloured.
Exactly. There's a lot of little niceties buried in the integration across the board. I'm convinced that many VSCode supporters have never used a true IDE because whenever I complain about VSCode's shortcomings I'm met with "why would you want that?". Sure, but this git example is a great one because for most of it I *don't* want it, but there's a lot of related bits that I *do* want.