I find it so weird that people are so bullish on the CLI form factor when they are literally just adding functionality that IDE based agents get for free. Stuff like improved diff tools and LSP support in the terminal instead of idk... just using a GUI/IDE? Pretty sure Cursor has had this for a while.
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, mo…
Claude Code gets native LSP support
281–290 of 352 posts
Re: Claude Code gets native LSP support
#282Earlier quoted context omitted.
Same shit, but Microsoft and Visual Studio. Like, the AI can't jump to definition! What are we fucking doing!?
Exactly! This is why LSP support should be huge, and I'm surprised it's just a line-item in a changelog.
Days fucking around with clangd for jump to definition to sometimes work. Sigh
Re: Claude Code gets native LSP support
#283Earlier quoted context omitted.
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
#284Hi, work on Claude Code here! Let me know if you have any feedback!
Re: Claude Code gets native LSP support
#285Interesting. I develop two projects and maintain a few. I haven't opened an IDE within the past two weeks. What do you do with an IDE? Stare as code is written, refactored, tested and debugged automatically?
Re: Claude Code gets native LSP support
#286I 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
Doesnt support windows though.
Re: Claude Code gets native LSP support
#287Earlier quoted context omitted.
I completely agree. Likewise I'm amazed Microsoft hasn't done it themselves for Roslyn and Copilot. Roslyn analyzers are so incredibly powerful, and it's being ignored. An explainer for others: Not only can analyzers act as basic linters, but transformations are built right in to them. Every time claude does search-and-replace to add a parameter I want to cry a little, this has been a solved science. Agents + Roslyn…
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.
It was one of the things that brought me to DataGrid in the first place
Re: Claude Code gets native LSP support
#288I 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…
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.
Re: Claude Code gets native LSP support
#289Earlier quoted context omitted.
This is something I notice often when using these tools (if this is what you are referring too). Like they will grep entire code bases to search for a word rather than search by symbol. I suppose they don't care to fix these types of things as it all adds up to paid tokens in the end. We have 50 years worth of progress on top of grep and grep is one of the worse ways to refactor a system. Nice to see LLM companies ar…
Only if they are not told how to search the codebase efficiently. All you need is an MCP server for code search. There's even LSP backed MCP servers now.
I'll have to check again because 6 months ago this stuff was pure trash and more frustrating than useful (beyond a boilerplate generate that also boils the ocean).
Re: Claude Code gets native LSP support
#290I 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…