{"version":"2.1.323","anchor":"lsp-server-start-failures-now-produce-an-actionable-message","canonical_anchor":"lsp-server-start-failures-now-produce-an-actionable-message","heading":"Language servers that fail to start now say what went wrong","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/lsp-server-start-failures-now-produce-an-actionable-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Language servers that fail to start now say what went wrong\n\nWhen a plugin's language server cannot start, Claude Code explains whether the program is missing or not runnable and where to look\n\n**Unclear.** Whether the message also appears in the interactive terminal interface is not settled.\n\n**What**\n\nSome plugins provide a language server, a helper program that understands a programming language and gives Claude Code code information. When one fails to start, Claude Code now builds a message that says which case it is:\n\n- The program could not be found.\n\n- The program exists but is not allowed to run.\n\n- Some other failure.\n\nThe message points to `claude --debug` or the Errors tab in `\/plugin`, and suggests disabling the plugin if you do not need it. In stream-json output it is sent as a warning notification, and in plain text output it is printed.\n\n**Why**\n\nA broken language server plugin now comes with a hint about how to fix it instead of failing quietly.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}