Configurable LSP server initialization timeout #2520
Description
Describe the feature or problem you'd like to solve
Large .NET repos (6000+ files, 100+ csproj projects) cause OmniSharp LSP to exceed the hardcoded 60s initialization timeout. The server needs 2-5 minutes for initial Roslyn workspace loading but gets killed before it finishes. This makes LSP unusable for enterprise monorepos.
Proposed solution
Add a lspInitTimeoutMs setting in config.json (default 60000 to preserve current behavior). Example: "lspInitTimeoutMs": 300000 for 5 minutes. Alternatively, retry the connection if the server process is still alive and consuming CPU.
Example prompts or workflows
Configure OmniSharp in lsp-config.json for a large .NET Framework + .NET 8 mixed-targeting repo → LSP server starts loading → times out at 60s → agent falls back to grep instead of having go-to-definition, find-references, and diagnostics. With a configurable timeout, the server would finish loading and provide full code intelligence.
Additional context
No response