tui: ability to view active lsps (or errors if failed to start) #1939

Activity

1. github-actions commented on Aug 14, 2025

   

   github-actionsBot

   on Aug 14, 2025 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • LSP options are not actually existing #324: LSP options are not actually existing (asks about LSP configuration and whether LSP feature exists)
   • How to get opencode to use LSP? #711: How to get opencode to use LSP? (about using LSP functionality)
   • LSP Diagnostics return nothing in large project #742: LSP Diagnostics return nothing in large project (about LSP diagnostics not working)
   • server.root is not a function #1590: server.root is not a function (about LSP server errors)

   Feel free to ignore if none of these address your specific case.

   👍React with 👍1Reacted by Nickolay Savchenko
2. rekram1-node

   assigned

   thdxr

   on Aug 14, 2025
3. rekram1-node

   marked Add user-visible LSP status indicators #3085 as a duplicate of this issue on Oct 10, 2025
4. isichei commented on Nov 22, 2025

   

   isichei

   on Nov 22, 2025

   Last edited by isichei

   More actions

   Hey, is issue currently being worked on? Was thinking something similar for a feature request and landed on this issue.

   Originally I thought it would be quite useful just to dump what available / enabled LSPs exist on the system when you call the status command. Something similar to Mason on Neovim. Was messing around and got to the pic below (where you can see opencode can only detect the gopls LSP).

   The implementation is just copying the interface you have for the formatters where enabled() gets Bun to call which on the relevant formatter command. So could be more complicated for a complete implementation for LSP Servers. Also I could imagine that this list could get to unwieldy so might need to be in a different command / status box.

   Anyway, thought I would add this comment if it is a thing you would want and I can continue on implementing it properly

   
5. rekram1-node commented on Nov 22, 2025

   

   rekram1-node

   on Nov 22, 2025

   CollaboratorAuthor

   More actions

   We do show the active lsps already

   

   But showing errors could be good, that example u showed is a bit too noisy
6. rekram1-node

   closed this as completedon Jan 20, 2026