{"version":"2.1.288","anchor":"lsp-servers-get-a-configurable-per-request-timeout-default","canonical_anchor":"lsp-servers-get-a-configurable-per-request-timeout-default","heading":"Language server requests now time out, with a configurable requestTimeout","tier":"use","area":"Language Servers","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/lsp-servers-get-a-configurable-per-request-timeout-default","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Language server requests now time out, with a configurable `requestTimeout`\n\nRequests to LSP language servers now give up after 60000 ms by default, which an LSP server's `requestTimeout` setting can change\n\n**Unclear.** Whether requests already waited 60000 milliseconds before this change, so that the default is unchanged, is not established.\n\n**What**\n\nAn 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.\n\n- Requests now time out after 60000 milliseconds (one minute) by default, with the error `no response after ...ms`.\n\n- 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.\n\n- Claude Code now tells servers it supports file-watch notifications (`didChangeWatchedFiles`), without dynamic registration.\n\n**Why**\n\nA 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.\n\n- Area: Language Servers\n- Names: `requestTimeout`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}