3 ms·

Very interesting approach. The folks at rift [0] worked on LSP as an integration point for AI coding. But I think they are focusing on other things now. Do you

Very interesting approach. The folks at rift [0] worked on LSP as an integration point for AI coding. But I think they are focusing on other things now. Do you think the LSP abstraction can support interactions beyond copilot style autocomplete? While that's a super helpful UX, it's also pretty narrow and limited. My project aider [1] provides a pair-programming UX, which allows complex interactions like asking for a change that will modify multiple files. Could LSP servers support more general AI coding like this? [0] https://github.com/morph-labs/rift https://github.com/morph-labs/rift [1] https://github.com/paul-gauthier/aider https://github.com/paul-gauthier/aider

smarvin2 2y ago
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-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
rane 2y ago
The problem with aider for me is that it works in the terminal, where as coding happens in the editor, where I most likely already have the file open I want to transform with LLM. I probably even have my cursor on the thing or can at least easily select the function etc. that needs to be changed. CopilotChat.nvim solves this somewhat elegantly for neovim, providing a streamlined UI to interact with an LLM in a way that allows accepting suggested diffs to your currently open buffer. The problem however is that it only works with GitHub's Copilot chat, as the name suggests. Not sure how well Copilot stacks up against gpt-4o for example but I'd imagine not that well. edit: Quick demo of CopilotChat.nvim: https://github.com/raine/ghtool/assets/11027/e8d5820b-eafb-43d6-9a1e-c10b63f7e8e1 https://github.com/raine/ghtool/assets/11027/e8d5820b-eafb-4... This is pretty much the kind of UI I'd want for interacting with LLMs, aside from the typical Copilot style ghost autocomplete.

smarvin2 2y ago

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-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

rane 2y ago

The problem with aider for me is that it works in the terminal, where as coding happens in the editor, where I most likely already have the file open I want to transform with LLM. I probably even have my cursor on the thing or can at least easily select the function etc. that needs to be changed. CopilotChat.nvim solves this somewhat elegantly for neovim, providing a streamlined UI to interact with an LLM in a way that allows accepting suggested diffs to your currently open buffer. The problem however is that it only works with GitHub's Copilot chat, as the name suggests. Not sure how well Copilot stacks up against gpt-4o for example but I'd imagine not that well. edit: Quick demo of CopilotChat.nvim: https://github.com/raine/ghtool/assets/11027/e8d5820b-eafb-43d6-9a1e-c10b63f7e8e1 https://github.com/raine/ghtool/assets/11027/e8d5820b-eafb-4... This is pretty much the kind of UI I'd want for interacting with LLMs, aside from the typical Copilot style ghost autocomplete.