Support for lsp ?

[bambanx]

Hello folks. This project have support for lsp server languages?
Thanks

[zemaj]

Not directly, at least not in the editor/LSP sense.

Today Code does not embed or manage language servers like rust-analyzer, tsserver, etc., and it does not expose an LSP endpoint for editor features.

The integration story right now is mainly:

• MCP client support, so Code can talk to external MCP servers/tools
• MCP/ACP server support for editor integrations (for example, the Zed integration)

So if you mean "can Code use language servers as a first-class feature for diagnostics/navigation/completions?" the answer is basically not today.

If you have a specific workflow in mind, please share it. For example:

• Code consuming diagnostics from an existing LSP server
• Exposing Code itself over LSP to an editor
• Language-aware project indexing/navigation inside the TUI

That would help us understand which kind of LSP support would be most useful.

[ivan-vilches]

in my case for :
-Improved debugging workflows

• semantic code understanding
• accurate navigation across the codebase
  thanks for the fast response

[cbusillo]

@zemaj when I read this, it makes me think of a feature I want, and kind of talked about before. I would love to see validation be able to external tools without editing code. I wrote a MCP that works with PyCharm Inspections. It would be awesome if those could be triggered in the background and fed into the context.

One of the issues I have found with Every Code's validation is the way it runs, it copies the files to inspect to a new tree. Therefore it cannot use the .markdownlint.json or whatever config files there are. With my setup, I have PyCharm setup to lint/check exactly the way I want (similar thing in IntelliJ). It would be nice to tie the validation into that instead of the current set of tools. Just a thought as I was reading this request.