{"version":"2.1.243","anchor":"nothing-in-the-shipped-code-starts-an-lsp-server","canonical_anchor":"nothing-in-the-shipped-code-starts-an-lsp-server","heading":"Nothing in the shipped code starts an LSP server","tier":"soon","area":"LSP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.243\/e\/nothing-in-the-shipped-code-starts-an-lsp-server","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.243","markdown":"### Nothing in the shipped code starts an LSP server\n\nLanguage-server support is fully built but nothing in the app ever starts one, so it stays dark.\n\n**What**\n\nThe language-server support has a manager with start, restart and shutdown entry points, but none of them are called anywhere in the shipped bundle. The LSP tool only ever reads connection status, so in practice no server is launched and the tool stays dark.\n\n**Details**\n\n- The manager exposes get, status, connected, ever-connected, wait-for-initialization, initialize, reinitialize and shutdown; only the four read-only ones have callers.\n- The tool's own code waits on initialization if status is pending and checks the ever-connected flag to decide whether it is enabled, but nothing triggers the initialization it waits for.\n- The initializer additionally returns early unless the `lspServers` feature flag is on, so even a future caller would be gated.\n- Same shape as the previous build; this is not new in 2.1.243.\n\n**Evidence**\n\n`[LSP MANAGER] initializeLspServerManager() called`\n\n- Area: LSP\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}