lsp-ai

Unless something's changed, every AI-backed language server I've tried in Helix suffers from the same limitation when it comes to completions: Suggestions aren't shown until the last language server has responded or timed-out. Your slowest language server determines how long you'll be waiting. The only project I know of that recognizes this is https://github.com/SilasMarvin/lsp-ai, which pivoted away from completions to chat interactions via code actions.

LSP-AI is meant to work with plugins. It can provide auto complete features without them, but to have the kind of experience Copilot provides with VS Code, you will need editor specific plugins. LSP-AI makes writing these plugins easier. Check out "The Case for LSP-AI" https://github.com/SilasMarvin/lsp-ai?tab=readme-ov-file#the... for more info on why I think that is true

Most editors should let you use multiple language severs at once, they merge the results together which can be annoying. LSP-AI is not meant to replace plugins. It works best when wrapped and used by a plugin. Our VS Code plugin is a great example of this: https://github.com/SilasMarvin/lsp-ai/wiki/Plugins LSP-AI abstracts complex implementation details like maintaining document / context parity and providing different LLM backends. I have a section no the Github Title: "The Case for LSP-AI" you might like: https://github.com/SilasMarvin/lsp-ai?tab=readme-ov-file#the...

You have complete control over the prompt configuration for LSP-AI. Feel free to check out the prompt section on our wiki: https://github.com/SilasMarvin/lsp-ai/wiki/Prompting It is very much still a work in progress, but I find the prompt I have listed as the default on that page does a good job of encouraging gpt-4o / llama 70b to provide only minimal completion suggestions.