Right now, every Claude Code user is running without LSP. That means every time you ask "where is processPayment defined?", Claude Code does what you'd do with a terminal. It greps. It searches text patterns across your entire codebase, reads through dozens of files, and tries to figure out which match is the actual definition.
It works. But it's slow, it's fuzzy, and on large codebases it regularly misses or gets confused. Search for User in a real project and you get 847 matches across 203 files: class definitions, variable names, comments, imports, CSS classes, SQL columns. The thing you actually wanted? Buried somewhere in the middle. Claude Code has to read through each match to narrow it down. That takes 30-60 seconds. Sometimes longer.
There's a feature that changes this entirely. It's called LSP, the Language Server Protocol. It's not enabled by default. It's not prominently documented. The setup requires a flag discovered through a GitHub issue, not the official docs. But once it's on, the same query ("where is processPayment defined?") returns the exact file and line number in 50 milliseconds. Not 30 seconds. Fifty milliseconds. With 100% accuracy.
That's not an incremental improvement. That's a category change in how Claude Code navigates your code.
TL;DR Claude Code ships without LSP enabled. Enabling it gives Claude the same code intelligence your IDE has: go-to-definition, find references, type info, real-time error detection. From my debug logs: ~50ms per query vs 30-60s with grep. Two minutes of setup. Jump to setup →
What You're Currently Running
By default, Claude Code navigates your codebase with text search tools: Grep , Glob , and Read . It's the same as having a very fast developer with grep and find at a terminal. Smart pattern matching, but fundamentally just matching text.
The core problem: grep treats code as text. But code is not text. It has structure, meaning, and relationships. When you ask "where is getUserById defined?", you want the one function definition, not the 50 places that call it plus the 12 comments that mention it. Grep can't tell the difference. LSP can.
What LSP Actually Is
Before 2016, every code editor had to build its own language support from scratch. VS Code needed a Python plugin. Vim needed a separate Python plugin. Emacs, Sublime, Atom — each one reinventing the same work. Twenty editors times fifty languages meant a thousand separate implementations, most of them incomplete.
... continue reading