Claude Code LSP

LexSiga 75 points 39 comments March 02, 2026
karanbansal.in · View on Hacker News

Discussion Highlights (20 comments)

re-thc

It’s not enabled by default because there are still bugs eg race condition issues. Check on GitHub.

user3939382

I built this myself for my agents a long time ago from ctags.

tietjens

I assume if this was working it would allow Claude to much more quickly gain an initial understanding of a repo on initial use, no?

ahofmann

This blog post is in the uncanny valley of "looks and sounds nice, but a bit too nice, could be useful, could be useless AI-slop, idk".

jascha_eng

It's not as secret as they make it sound. Documented here: https://code.claude.com/docs/en/discover-plugins#code-intell... Also the post is definitely AI written partially, but still useful I suppose.

_joel

I'd test it but Claude is down

smallerfish

In the same way that good AI coding requires testing, project management and architecture, good AI writing requires you to fill the editor role. Be ruthless. Read line by line. By all means tell the agent to fix stuff. If you don't do this, your blog posts sound generic and lazy.

OJFord

https://code.claude.com/docs/en/discover-plugins#code-intell... Why are they doing this with a client plugin per server? It's antithetical to the whole point of LSP? (At least they're reusing existing servers I suppose, but it stops me using whatever arbitrary one I want, as I could if there was just a single client with arbitrary configuration.)

tempaccount420

LSPs suck. Compilers should be able to re-use their cache for queries, interfaced with through a simple CLI. They should not need more RAM than what the compiler uses. Most LSPs don't work well for big projects or with non-standard setups like Bazel. Edit: is this really so controversial it has to be downvoted?

AntiDyatlov

I wish AI written submissions were banned.

johnmiroki

I never got it working for even once. it's an epic failure on Anthropic

danslo

Not sure if it's Claude Code or golsp, but I had to uninstall the plugin. Regularly makes Claude Code crash with golsp going to 100% CPU usage.

dayglo

I had great results using this for the past few months, it’s the same idea but implemented as an MCP: https://github.com/oraios/serena

theknarf

That is when the LSP works, now you've just introduced another thing that may fail.

jasonjmcghee

For what's it's worth I never enabled anything and it proactively encouraged me to install various lsp plugins and prompted me to accept to install in most languages I've tried.

steeleyespan

“ That's not an incremental improvement. That's a category change in how Claude Code navigates your code.” Literally everything is written by AI now, even top HN articles.

colinhb

From the intro section: > That's not an incremental improvement. That's a category change in how Claude Code navigates your code. I don’t know anything about the human(s) behind this project, assuming there are any, and intend no malice towards them, but when I encounter language like this, it just kills my enthusiasm for a project. I wonder if that reaction is now, or will become, a majority one, and that AI flavoured language and products will face some audience headwinds if there aren’t indications of some level of human authorship / editing.

rvcdbn

It's not hidden at all, Claude pushes it even tho it poisons the context after every edit with false positives because it's always out of date. This feature should be hidden given how half baked it is.

ndom91

Had trouble with their two marketplace's as there's also another `anthropics-claude-code`. Here's the commands to install the correct marketplace and LSP plugins: /plugin marketplace add anthropics/claude-plugins-official /plugin install typescript-lsp@claude-plugin-directory See all LSP's names here: https://code.claude.com/docs/en/discover-plugins#code-intell...

LexSiga

since its flagged - gotta comment; I am not the author of the post. I was reading it in passing and thought it was interesting enough to submit. Indeeed did not paid enough attention as to how much "ai written" it was.

Semantic search powered by Rivestack pgvector
3,471 stories · 32,344 chunks indexed