Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.287 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.288entry #28

Claude Code v2.1.288 ·

Language server requests now time out, with a configurable requestTimeout

Requests to LSP language servers now give up after 60000 ms by default, which an LSP server's requestTimeout setting can change

Group of 2 Use it now Notable New Features
JSON All of v2.1.288
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Language ServersArea: what it touches
New FeaturesKind: in v2.1.288,
What probably matters to youSection of the release

What

An LSP server, or language server, is a helper program that gives code intelligence such as definitions and references. Claude Code's requests to these servers used to wait with no limit.

  • Requests now time out after 60000 milliseconds (one minute) by default, with the error no response after ...ms.
  • The LSP server configuration gains an optional requestTimeout field: Maximum time to wait for the server to answer a request (milliseconds). Defaults to 60000. Before, only startup and shutdown timeouts could be set.
  • Claude Code now tells servers it supports file-watch notifications (didChangeWatchedFiles), without dynamic registration.

Why

A language server that hangs no longer blocks the call forever. If you use a slow server, you can raise the limit, and you can lower it to fail sooner.

Read from
Names in the bundlerequestTimeout
What the documentation says
Documented inapi/build-with-claude/mid-conversation-effort-example
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether requests already waited 60000 milliseconds before this change, so that the default is unchanged, is not established.

See this entry in the whole of v2.1.288 →

Feedback