Give Claude an LSP
Drive AI agents through a million lines of code you did not write. Recon, surgical navigation, codemods, characterization tests, and a toolkit of four reusable skills you keep.
A quick one, and a tip I wish more people knew about. Claude Code (Codex too, and others) can use a Language Server Protocol server if one is installed. Symbols, interfaces, references, the same machinery that powers IntelliSense in your editor. Instead of grepping its way through a million lines looking for the thing that implements an interface, the agent asks the language server and gets the answer.
That matters here. Ripping Copilot out means chasing down every file that touches a handful of interfaces, and an LSP makes that a lookup rather than a search.
So I ask Claude directly: do you have access to an LSP here? If not, how do I install one? Is TypeScript's robust enough for us to work with? I have a guess at the answer, since this is Microsoft's language inside Microsoft's editor, but I want to see it confirmed.
Confirmed. The TypeScript LSP is present and connected, and Claude points out it is literally what VS Code itself runs on. If you are in JetBrains or some other environment and the answer comes back no, Claude will hand you the install steps for your setup.
One wrinkle: per our CLAUDE.md, navigation is supposed to go through the map we built, so day to day the LSP is a backup. But it is there when the map runs out.
If you are working in a big .NET or Java codebase and you do not have an LSP hooked up, go do that. It makes working with Claude or Codex or any of these tools much faster.
Drive AI agents through a million lines of code you did not write. Recon, surgical navigation, codemods, characterization tests, and a toolkit of four reusable skills you keep.