Protocols
Saved & recent

LSP initialization

Also called: initialize request, initialized notification

LSP initialization establishes which editor and language-server features can work together. In the inspected 3.18 specification, the editor sends initialize with its capabilities and receives the server’s capabilities. Optional features need explicit support; connecting to a language server does not imply that every language operation is available.

For example, a server can advertise completion support while leaving semantic tokens unavailable. After the initialize response, the editor sends the initialized notification before ordinary feature requests. This ordering gives both sides a shared starting point, while later capability registration can adjust supported features where the client permits it.

Read first
Language Server Protocol
Related
Language Server Protocol, Capability negotiation, LSP completion
Further reading
editor language server initialize · client capabilities response · completion supported initialized notification textDocument/completion semantic tokens unavailable LSP 3.18 · advertised features
LSP 3.18 exchanges capabilities during initialization before the editor starts ordinary language-feature requests.

View in the full Protocols collection