No rename symbol? What am I missing? It seems like a no brainer.
Claude Code gets native LSP support
151–160 of 352 posts
Re: Claude Code gets native LSP support
#152Earlier quoted context omitted.
Well you need to use context space somehow, to tell Claude that the LSP CLI exists and how to use it.
It takes a dozen tokens to put "when you need to do X, run `foo --help` and use it" in your CLAUDE.md. Plenty of MCPs and plugins and whatnot out there idly consuming 5-25k tokens 24/7. How is that the same?
I do it all the time. I have several MCPs configured but only enable them on demand.
Re: Claude Code gets native LSP support
#153I am super bullish on claude code / codex cli + LSP and other deterministic codemod and code intelligence tools. I was playing around with codex this weekend and honestly having a great time (my opinion of it has 180'd since gpt-5.2(-codex) came out) but I was getting annoyed at it because it kept missing references when I asked it to rename or move symbols. So I built a skill that teaches it to use rope for mechanic…
Are you having a positive experience with Codex compared to Claude Code? Codex in my brief experience was... not good w/ 5.1
Re: Claude Code gets native LSP support
#154I 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.
$x$.foo($args$)
Where you add filters like x's type is a subclass of some class, and args stands for 0-n arguments.You can also access the full intellij API via groovy scripts in the filters or when computing replacement variables, if you really want.
Though most of the time built in refactors like 'extract to _' or 'move to' or 'inline' or 'change type signature' or 'find duplicates' are enough.
Re: Claude Code gets native LSP support
#155Re: Claude Code gets native LSP support
#156I should know this, but what's LSP? Language Server Protocol - I can read. But what's that?
It's the protocol that VSC made to speak to programs that do code analysis and is the basis of goto definition, autocomplete, refactorings etc. It's used by most smaller editors so they can backpack off of the efforts languages make to be usable in VSC. (Vim, Emacs, Zed, etc)
Re: Claude Code gets native LSP support
#157I 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…
LSP supports refactoring commands
Re: Claude Code gets native LSP support
#158I 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…
Re: Claude Code gets native LSP support
#159Earlier 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…
Re: Claude Code gets native LSP support
#160Earlier quoted context omitted.
Perhaps because you are searching for "mcp" and not "lsp"?
LOL yeah that would be a solid guess but I just sanity checked and I messed it up only in the comment, in Claude Code when I search for "lsp" I still get no matches.