Compiler intelligence over LSP
2ot exposes the same parser, semantic analysis and diagnostic stack through a standard Language Server Protocol surface.
A dedicated protocol surface
The LSP route is a first-class part of the 2ot command surface. It stays separate from the vendor runtimes and exposes compiler-backed language operations over the standard protocol, so clients can consume 2ot analysis without depending on vendor-specific automation APIs.
Diagnostics from the compiler
LSP diagnostics come from the same compiler analysis used by the fast diagnostic path, keeping language-server feedback consistent with command-line analysis rather than maintaining a second diagnostic implementation.
Semantic information
Resolved symbols, types, call relationships and semantic token information can be surfaced through LSP without exposing the internal compiler representation as a public API.
Workspace-aware operations
Because requests are backed by the workspace semantic model, operations such as rename and symbol resolution can reason about scope and cross-file collisions instead of falling back to text-only replacement.
One analysis stack
CLI diagnostics, LSP requests and agent-facing tooling all sit on top of the same compiler capabilities. That keeps language behavior consistent across interactive, automated and AI-assisted workflows.