[FEATURE] disable lsp

Resolved 💬 3 comments Opened Dec 23, 2025 by joshribakoff Closed Feb 14, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

I have often seen in other tools where the LSP just feeds the agent lagging information which actually derails the agent. I recently saw the announcement that you were adding LSP support, and this is a request to please ensure that it is disabled by default or can be disabled by a power user at the very least. Or a request to please consider this failure mode and avoid it.

Proposed Solution

It works perfectly fine now just run the type checker command after completing a batch of changes. You are guaranteed to get fresh state. You are introducing asynchronicity in the form of the LSP, which is an asynchronous external process with its own state. It sounds like we’re gonna get the same race conditions now in Claude Code.

This is a user space level concern. I dislike how opinionated you are being about it.

We can already run an LSP and expose it over MCP. You can already call tools via the command line. Tools like TSC or TS morph for example. I understand the impetus to automate it so it works out of the box, but that will be no good if it comes with the failure modes so please consider those and that is my request.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗