LSPs should expose their api through shell commands - then integrating it with any LLM would be trivial. And it would also be very useful for humans.

I haven't come across a case where it has used the LSP yet.

Opus 4.5 is fairly consistent in running QA at proper times. Lint checks and all are already incorporated into a standard & native processes outside of IDE. I think lookup can be useful when definitions are hidden deep in hard to reach places on my disk... hasn't been a problem though the agent usually finds what it needs.

Anyway, here is what it stated it could do:

    > Do you have access to an lsp tool?

     Yes, I have an LSP tool with these operations:

    - goToDefinition - Find where a symbol is defined
    - findReferences - Find all references to a symbol
    - hover - Get documentation/type info for a symbol
    - documentSymbol - Get all symbols in a file
    - workspaceSymbol - Search for symbols across the workspace
    - goToImplementation - Find implementations of an interface/abstract method
    - prepareCallHierarchy - Get call hierarchy item at a position
    - incomingCalls - Find what calls a function
    - outgoingCalls - Find what a function calls

So they moved coding AIs from the IDE into a standalone CLI and now are building an IDE around the CLI?

  Added gift tag pictogram for year-end promotion message

What's that? We all want a promotion on Claude Code!

dumb question,how to use it? claude is a cli tool,not an editor,why is lsp relevant?

Amazing how long this took. Serena has been doing a not bad job of helping solve this issue. But this has been an obvious built in for agents for some time now. https://github.com/oraios/serena

It has been in the source code for like two months. I've been using it for a while now.

I was hoping LSP support would be implemented. I know there are existing MCP servers that can do something kind of similar, but I doubt the agent would be smart enough to consistently utilize the LSP MCP. Here's hoping for less greps.

The typescript-lsp (and others?) is missing a critical part of LSPs whcih is the diagnostics for real-time errors and warnings. So you still need to run a linter, tsc, etc. to generate those sadly.

If you want to explore the ecosystem of Claude Code plugins, see https://claude-plugins.dev/

With a fair disclaimer, that it is very easy to vibe-code a skill oneself, with both pros (you can create one just for you!) and cons (if you look online, these are of any quality, quite a few with some hard-coded versions or practices).