feature: in-process LSP to interact with `opencode`

[nickjvandyke]

Opening the floor to ideas for an in-process LSP that interacts with opencode 😁

Validity

Pros

• Primary goal of this plugin is supplementing editor-first workflows, and LSPs are essentially first-class citizens in editors
• Familiar UX
• ?

Cons

• Slight departure from opencode-TUI-only experience; bit scattered
• LSPs are generally deterministic and reliable; LLMs, not as much
• ?

Handlers

• Code actions
  • Ask opencode to fix the diagnostic under the cursor
  • ?
• Hover
  • Ask opencode to explain the symbol under the cursor
    • I say "symbol" but really it works for anything, like literals
• Code lens/inlay hints
  • Some kind of useful contextual info?
• Completion
  • Inline
    • Not sure how much this adds over e.g. copilot.lua. opencode can probably gather more context for a better suggestion, but is that worth the speed tradeoff?
• ?

Describe alternatives you've considered

Manually prompting opencode with whatever the LSP handlers would do. Possibly via non-LSP keymaps.

Additional context

Presumably some ideas in https://github.com/SilasMarvin/lsp-ai, but I think we could do better with nvim and opencode specificity.

---

Please offer ideas and feedback!

[SearidangPa]

Hi, first of all I'm such a big fan of this plugin. The interface is so incredibly well-thought out.

• I like this Hover to Ask opencode to explain the symbol under the cursor
• I would be a bit hesitant to use this Ask opencode to fix the diagnostic under the cursor. I would, however, like to it be a plan agent mode thing with a confirmation yes/No.

If there is anything you would like help with and think other people can help, please let me know if there is any system for this such as tagged label on the issue.

[nickjvandyke]

Thank you for your kind words and thoughts @SearidangPa 🙂

I would, however, like to it be a plan agent mode thing with a confirmation yes/No.

Yeah, I assume opencode run under the hood does bypass permissions etc... What would you think if the plugin sent the message to your running opencode (as the rest of the plugin does)? However I'm concerned that could pollute a possibly unrelated conversation.

I know opencode run has the --attach flag - I wonder if that would integrate permissions? I mean to try it regardless, to improve speed.

[tranquangdat-w]

Thank you for your kind words and thoughts @SearidangPa 🙂

I would, however, like to it be a plan agent mode thing with a confirmation yes/No.

Yeah, I assume opencode run under the hood does bypass permissions etc... What would you think if the plugin sent the message to your running opencode (as the rest of the plugin does)? However I'm concerned that could pollute a possibly unrelated conversation.

I know opencode run has the --attach flag - I wonder if that would integrate permissions? I mean to try it regardless, to improve speed.

opencode web --port 4096
opencode attach http://localhost:4096

can using attach in opencode, and after that, the web and tui is simultaneously, sharing the same sessions and state. This is alternative for that features.