Analyzed: March 31, 2026 leak snapshot

​
LSP surface in this snapshot

The LSP integration spans:
  • src/tools/LSPTool/
  • src/services/lsp/LSPClient.ts
  • src/services/lsp/LSPServerManager.ts
  • src/services/lsp/manager.ts
  • src/services/lsp/passiveFeedback.ts
The tool itself is only registered when ENABLE_LSP_TOOL is truthy.

​
What the LSP tool adds

The LSP path gives Claude Code a semantic code-query channel separate from grep and plain file reads. That means the agent can, in principle, ask for symbol-aware or language-server-backed context instead of relying only on text search.

​
Why this matters architecturally

The codebase already has strong text tools. LSP exists to supplement them where lexical search is not enough. Typical value cases are implied by the module names:
  • symbol context
  • diagnostics
  • formatter helpers
  • semantic navigation
Exact request fields live in src/tools/LSPTool/schemas.ts.

​
Operational caveat

Because the tool is feature-gated and depends on external language-server processes, its presence in source is stronger than its guarantee at runtime. Treat it as optional infrastructure, not a universal primitive.