Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.243entry #1

Claude Code v2.1.243 ·

Nothing in the shipped code starts an LSP server

Language-server support is fully built but nothing in the app ever starts one, so it stays dark.

Nothing to try yet Notable In Development
JSON All of v2.1.243
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
5Signal: worth watching, 1 to 5
LSPArea: what it touches
In DevelopmentKind: in v2.1.243,
What probably matters to youSection of the release

A language-server manager with start, restart and shutdown exists in the bundle, but nothing calls it and the LSP tool only reads connection status.

What

The 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.

Details
  • The manager exposes get, status, connected, ever-connected, wait-for-initialization, initialize, reinitialize and shutdown; only the four read-only ones have callers.
  • 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.
  • The initializer additionally returns early unless the lspServers feature flag is on, so even a future caller would be gated.
  • Same shape as the previous build; this is not new in 2.1.243.
Evidence

[LSP MANAGER] initializeLspServerManager() called

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.243 →

Feedback