[FEATURE]: Force LSP usage #6281

Open
opened 2026-02-16 18:02:35 -05:00 by yindo · 0 comments
Owner

Originally created by @YPares on GitHub (Jan 15, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Currently, some LSPs are auto-activated based on the project layout.

For instance, TS LSP is activated it seems if there is a package.json at the root of the repo with a typescript dependency, and a node_modules folder.

In my case, I'm working in a monorepo where the typescript workspace is one level lower. Would it possible to force-activate via config the use of the TS LSP (even if it means I need to put it in the PATH myself).

Originally created by @YPares on GitHub (Jan 15, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request Currently, some LSPs are auto-activated based on the project layout. For instance, TS LSP is activated it seems if there is a `package.json` at the **root** of the repo with a typescript dependency, and a `node_modules` folder. In my case, I'm working in a monorepo where the typescript workspace is one level lower. Would it possible to force-activate via config the use of the TS LSP (even if it means I need to put it in the PATH myself).
yindo added the discussion label 2026-02-16 18:02:35 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#6281